Your question here is a little more related to servlets than GWT RPC.

The GWT RPC mechanism sits on top of servlets (on top of the doPost method to 
be exact) and 
therefore works in much the same way (ie: no serialization guarantees). 
Whenever any client invokes 
an RPC method, that method will be invoked on the RPC Servlet. However, this 
may be limited by:

1) The number of connections a client is allowed open by the browser
2) The number of processor threads allocated on the server

It's generally considered "good" to assume the client can only have 2 
connections open, since this 
is the minimum number.

On the other side of the net: most servlet containers only create one Servlet 
instance per 
ServletContext and route all requests to that instance (or at least per related 
entry in the web.xml 
file). The number of threads that are available to process requests (and how 
these threads are 
managed) is dependent on the servlet container and it's configuration.

In short, you should make sure all of your RPC methods are reentrant and your 
Servlets are 
"logically" stateless (ie: they should not have any mutable fields).

Hope this helps.
//J

David Given wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi,
> 
> Does anyone have any information on threading issues as applied to the
> RPC server code? I've been unable to find anything on the 'net.
> 
> In particular, I need to know about any synchronisation guarantees
> between RPC function handlers. What happens if the client makes two RPC
> requests at the same time? Am I guaranteed to get all requests from a
> single session serialised? What about requests from multiple sessions? I
> assume that since all this is being handled by a servlet, eventually,
> the servlet may allocate new threads as it sees fit --- but I can't find
> any information about what it *actually* does.
> 
> Any information gratefully appreciated...
> 
> - --
> ┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
> │
> │ "They laughed at Newton. They laughed at Einstein. Of course, they
> │ also laughed at Bozo the Clown." --- Carl Sagan
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iEYEARECAAYFAkpXLZoACgkQf9E0noFvlzhlSQCgs3QlfUDKlZjsw+mzmaaHU/eS
> zAYAniWsoRBn4divs+T/B6HdT4NP6Y5w
> =PDpc
> -----END PGP SIGNATURE-----
> 
> > 
> 

--~--~---------~--~----~------------~-------~--~----~
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