That's a servlet lifecycle question, a servlet engine ( f.e. Tomcat )
may create one or many instances of a servlet, as needed. At init, one
will be created.
There's no way to control or configure this; and this behaviour is
determined by servlet specification, nor by GWT

If you want to assign some resources /objects to only one session, use
this on the servlet code :

getThreadLocalRequest().getSession().setAttribute("resource",
resoure);


Oskar

Pd. so much time without posting here.... excuse me !




On 23 mar, 21:32, Arturo <[email protected]> wrote:
> Hi all,
> may be my question sounds a bit strange, but 'cause I'm approaching an
> important project implementation I want to be sure I understood GWT
> mechanism.
>
> My problem is the following:
>  - I've created a GWT application that uses an RPC Service for
> accessing data from database.
> In a single user environment it works fine.
>
> Than I tested a multiuser access and I started from accessing the
> deployed application from two different web browser (Firefox and IE)
> at the same time (approx...) from the same PC (same ip address).
> What I found out is that the Remote Implementation object, that is
> subclass of RemoteServiceServlet seems to be the same for both web
> page !
> If I put the remote instance out (System.out.println(this)) if
> discover that is just the same. Of course this creates a lot of
> problems to me.
>
> Am I missing something or is a normal behaviour because it use a sort
> of session context ?
>
> My worries is what happens when different end-users access to my
> application, once deployed !
>
> Any help would be appreciated.
>
> Arturo
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to