Depends on who initiates the service. If it's the other machine (not the web server), then in general no, unless you run a custom web server on it that will convert resource requests (images or JS scripts only) into commands (the authentication information will have to be encoded in the names in addition to the commands if you have to have authenticated service) . This is quite complicated.
If the web server can control the service, then a simple authenticated RPC call will suffice. Don't bother with cookies if you are using RPC. http://code.google.com/p/google-web-toolkit/wiki/RpcAuth On Sat, Apr 18, 2009 at 11:16 PM, joshmo <captainj...@gmail.com> wrote: > > What I want to do is log in to an application. Once logged in, the > user clicks a button to start a service. Then the user will remain > logged in and monitor the service. The service is used for > transferring files a different computer to the computer the web server > is running on. The web page will update every minute with status of > server and bandwidth used. User can log out and log in the next day > to the same service and continue to monitor the service. > > Is this possible? I have been reading about setting a cookie with a > session id but I don't know if this is going to work or not. Does > anyone know if you can maintain session state with a service and that > service continues to run in a daemon thread even if the user logs out? > > Thanks for any response. > > > > --~--~---------~--~----~------------~-------~--~----~ 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 google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
