No, each request does not get it's own instance of a servlet. If you
must store user data on the server between requests, put it in session
or in the database.
On Fri, Aug 7, 2009 at 12:28 AM, Parmeet Kohliparmeet.ko...@gmail.com wrote:
I seem to be facing a similar problem. The class i have
I seem to be facing a similar problem. The class i have created at the
server end ( extends RemoteServiceServlet and implements the interface
at the client end ) does have state and methods which depend on each
other. IS A NEW OBJECT NOT INSTANTIATED FROM THIS CLASS EVERY TIME A
NEW USER CALLS IT
Say if users using different services concurrently and yet I have
grouped the services together, will my web application crash (it can't
tell which service for whom) ?
Are you saying that your servlets are stateful? That would indeed be a
problem. You shouldn't have any member variables in
Hi fellow members,
I have been following examples found on the web to build my web
application with RPC mechanism.
My web application has quite a few services. By right, each service
should have its own class files on both client and server side. But
this way will result in a lot of class
