Reinier, Why do you advocate rewriting your web stack's session management when you could just as easily let it continue to use the cookie as long as you validate that it matches the sessionid passed up via the parameter list? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
- Re: SecureRemoteService and Servlet. The battle agains... gregor
- Re: SecureRemoteService and Servlet. The battle a... Reinier Zwitserloot
- Re: SecureRemoteService and Servlet. The batt... gregor
- Re: SecureRemoteService and Servlet. The ... Reinier Zwitserloot
- Re: SecureRemoteService and Servlet. ... Patrick Ratelband
- Re: SecureRemoteService and Serv... Reinier Zwitserloot
- Re: SecureRemoteService and Serv... Patrick Ratelband
- Re: SecureRemoteService and Serv... gregor
- Re: SecureRemoteService and Serv... jhulford
- Re: SecureRemoteService and Serv... gregor
- Re: SecureRemoteService and Serv... quentin
- Re: SecureRemoteService and Serv... Reinier Zwitserloot
- Re: SecureRemoteService and Serv... quentin
- Re: SecureRemoteService and Serv... Reinier Zwitserloot
- Re: SecureRemoteService and Serv... Patrick Ratelband
- Re: SecureRemoteService and Serv... quentin
- Re: SecureRemoteService and Serv... jhulford
- Re: SecureRemoteService and Serv... jossey
- Re: SecureRemoteService and Serv... jhulford