Hi Markus, Is it possible the SessionId Cookie hasn't been sent to the client when the second method is invoked? You may need to force the Server to create the HttpSession object and send the Cookie in your host page (or before you reach it).
Basically any call to HttpServletRequest.getSession() should create the session and assign an ID to it, but until the response has been sent to the client, the browser won't have knowledge of that Session. Let me know if thats not the problem. //J Markus wrote: > Hello > > I have following problem with my application. > If I make generally rpc calls during RemoteServiceServlet all is fine, > if I use: this.getThreadLocalRequest().getSession().getId() I allways > get the same sessionID back > and I can work with it. > > No I have following case. I added a long polling mechanism to get > actual data from the server. > Exactly I have a RemoteServiceServlet which is waiting for data. > > Now the problem: > If I make another rpc call to another RemoteServiceServlet, during the > long polling servlet is running, > I get on that second Servlet, a new sessionID if I do > this.getThreadLocalRequest().getSession().getId(). > > How can it be, that I get 2 different sessionIDs with the same > application? > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
