If you're using Spring, you might want to take a look at Spring Security. It handles session management and role based security for you. You can then couple that with a check against the server side if the user's session is still valid. You can either do this with a Timer (if you want to time them out right away) or build it into your page/screen changing system.
We do the latter using a history management filter whereby history changes go through a number of filters before arriving at the correct handler. If the user check filter catches the user isn't logged in, we show them the login screen. -- Arthur Kalmenson On Mon, Apr 20, 2009 at 9:06 AM, Mark <cattaba...@gmail.com> wrote: > > Well appreciated comrades > > The intention was never to drive you to write code but to give me a > peek for i am raw in this field > > I have gotten that and i appreciate > > Thank you again. > > On Apr 20, 11:44 am, Vitali Lovich <vlov...@gmail.com> wrote: >> Not to mention that I already described how you I did exactly what you >> asked. However, you are expected to at least try & write your own code >> since people do tend to have their own things to work on. >> >> On Mon, Apr 20, 2009 at 4:28 AM, Salvador Diaz >> <diaz.salva...@gmail.com>wrote: >> >> >> >> > > How do i create it on the server? >> >> > Google it ;) >> >> > More seriously, you can't just ask all of your questions in a forum >> > and expect that people will write the code for you, you have to show >> > you're doing some efforts, so I'll help you and give you some >> > interesting reading: >> >> > >> >> >http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/g...()<http://google-web-toolkit.googlecode.com/svn/javadoc/1.6/com/google/g...> >> >> >http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/H...()<http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/H...> >> >> >http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/H...()<http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/H...> >> >> > That should be enough to let you implement the automatic logout >> > feature >> >> > Cheers, >> >> > Salvador >> >> > On Apr 20, 10:13 am, Mark <cattaba...@gmail.com> wrote: >> > > I like the second option because i love being fancy :=) >> >> > > How do i create it on the server? >> >> > > Thank you - enlightening >> >> > > On Apr 20, 10:03 am, Salvador Diaz <diaz.salva...@gmail.com> wrote: >> >> > > > You should set the session timeout in your servlet container to >> > > > whatever you want it to be. When the session expires, any RPC in a >> > > > logged in client will fail, so that should be enough. >> >> > > > If you want to be fancy, create a serializable timeout exception, and >> > > > then when you catch it client-side, logout the user and show him the >> > > > login prompt >> >> > > > Cheers, >> >> > > > Salvador >> >> > > > On Apr 20, 7:38 am, Mark <cattaba...@gmail.com> wrote: >> >> > > > > Hi All; >> >> > > > > I earlier requested help in regard tothe above subject but i have >> > > > > waited in vain. >> >> > > > > I am new to GWT and I am working on a data critical application where >> > > > > security is imperative. >> >> > > > > I want to implement an automatic logout feature if the application >> > > > > does not receive activity for n - minutes!!!! >> >> > > > > Help out >> >> > > > > Mark > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
