Thank you cokol, I think I got, what I needed. Thanks for your help!
Greets Alex On 21 Jul., 22:11, cokol <[email protected]> wrote: > hi, you dont need to care for session ids, unless cookies are > disabled, since almost every servlet container (tomcat, appengine,etc) > creates a new sessionid for every request it does not recognize and > this sessionid is sent back with a cookie. from now on, the browser > automatically sends a cookie for EVERY request from the page, > including RPC calls - so you just save whatever you want on the > serverside via request.getSession().setAttribute("USER",user); it will > work out > > if you want to support users with cookies disabled, this would be a > bit tricky and needs some conventions.... > > On 21 Jul., 16:41, AlexG <[email protected]> wrote: > > > Hi @ all, > > > I want to build a Suer-Management System, where Users can Login und > > persist personal Data. > > I found this article below, as a little how-to-guide. > > >http://code.google.com/p/google-web-toolkit-incubator/wiki/LoginSecur... > > > What I want, is to save a session id on the client, recieved from the > > server when logging in. Then for > > future RPC´s I want to automatically send the session-Id whit it, to > > identify the users. > > In the tutorial they say, send the session-Id within the payload of > > future RPC. > > > My question is, how can I do this? How can I modify the payload, to > > send the session-Id with the RPC? > > The following question will be, how can I read this Id from the > > payload on the server? > > > It would be nice if someone can help me. > > > Greets > > Alex > > -- 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.
