Thanks for the reply. I will definitely look at this for authentication. Although this doesn't appear to be the full answer to my question. Maybe I just don't understand some fundamental piece. I am very familiar with java programming but haven't done too much of the web stuff. I am used to rmi iiop, and swing/awt thin clients. The service will be run on the web server. Whenever I log in for the first time using this authentication method, I kick off a thread. I want to be able to log out and reconnect the next day and gain control and monitor that same thread (Timertask) that I started the previous day. I am guessing since I kicked the thread off in the Impl (service running on the web server) class, this thread is running inside of the web server (tomcat). Do I have to set up a service on the machine that my Impl class can connect to using rmi or something. I didn't want to do this as it adds an extra layer to the connection so I was hoping to have just the Impl class with a timertask that I can just control from the web and it maintains state and continues to run. When I log out, will the thread be garbage collected or can I log back into the same object running the thread and control/monitor the same thread?
Thanks again for any reply. On Sun, Apr 19, 2009 at 6:32 AM, Vitali Lovich <vlov...@gmail.com> wrote: > 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 -~----------~----~----~----~------~----~------~--~---
