Hi, Generally with J2EE serverside (or .net) your session object has a one to one relation ship with your user, it is communicated to the server one of two ways; 1) As a cookie (what your seeing with the session id in the cookie) 2) As a cgi parameter of the url (ie http://foo.com/index.html?jsessionid=987298429847) [for users who have cookies turned off]
On the server the session is looked up and added to your HttpRequest (getThreadLocalRequest) object before your code (regular Servlet onService or rpc method) does anything. You can use the session paradigm to store state full information (like the users name Chris) when the protocol is stateless (http). If you don't need state full information just ignore the session api. Cheers, Scott On Apr 15, 2:05 pm, "[email protected]" <[email protected]> wrote: > To speak the truth i don't know about what video you are talking > about, > but I'm quite satisfied that the topics title sounds clever )))) > > On Apr 15, 2:38 am, matttai <[email protected]> wrote: > > > I was unsure if this topic title was a clever play on a popular video > > circulating the internet. If so very clever :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
