-----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... - -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── 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 -~----------~----~----~----~------~----~------~--~---
