First, decide whether your clients can simply talk HTTP to the server (using apache commons httpclient, or something like it), or whether you'd gain from using a web service.
Second, map out what the servlet or web service has to do
Third, make decisions about security: where on your network will the server sit, can it be seen by anyone other than your clients (think testing, for example), what should it do if it is
Once you have answers to those questions, you'll know what shape your server application is and you can go back to "Can Glassfish help..." with the right questions
[Message sent by forum member 'pdfalcon' (pdfalcon)]
http://forums.java.net/jive/thread.jspa?messageID=351297