What about the following idea. The user request some action that needs to go to the server, in your rpc in the server side you send an Exception, for example TimedOutException and in your client code check in the onFailure method which is the exception, if the Exception is TimedOutException you redirect your user to the logout page.
On 24 jun, 12:50, Prakash <prakash.masilam...@gmail.com> wrote: > Hi Sunny, > > http://en.wikipedia.org/wiki/Comet_(programming) : gives overview abt > server side push. > > And also you can use HttpSessionListener to listen for session expiry > event, instead of using timer to detect the same. > > -Prakash M. > > On Jun 24, 6:38 pm, StrongSteve <swe.sta...@gmail.com> wrote: > > > @Sunny: > > Although you found the thread on the server there is no way (except > > polling) to inform the user/client/browser about the occurrence of > > this event. > > > @Bruno: > > Nice solution, but it is basically a counter/timer on the client side. > > Please correct me if I am wrong. You specify a time and after the time > > has run off, the user gets logged off. Except if his is clicking a > > special button in the small window of opportunity. > > > Basically what you all want to do is to kick the user after he/she has > > worked for an amount of time. > > From my point of view this differs from the concept of session. Those > > define a timeout of inactivity time - not a maximum working time > > (There is a great difference in limiting the time a user has to max. > > 30 minutes or set the maximum inactivity time to 30 minutes). If this > > time is reached the session object is removed from the server. Why? In > > order to free up resources on the server side. > > In your client timer solutions how to you ensure that the session > > object gets removed from the server? > > In order for your solution to work properly you need to start your > > server with an infinite session timeout and this can very easily be a > > problem if your session-object-free-up mechanism fails. > > > Greetings > > Stefan > > > On 24 Jun., 14:51, Bruno Lopes <bruno.lourenco.lo...@gmail.com> wrote: > > > > Hi > > > > I have the solution :) > > > > Check the file atttached > > > > Hope it helps :) > > > > Bruno > > > > On Thu, Jun 24, 2010 at 12:56 PM, Sunny <pratik.sachd...@gmail.com> wrote: > > > > Hi Stefan, > > > > Thanks for the suggestion but i cannot do that because that will > > > > create too much of network traffic. > > > > Mean While i have found a way to identify the DAEMON THREAD for the > > > > session that has recently expired > > > > but i still need a way to send the message to correct widget, in my > > > > case a Label, to show the message to the user. > > > > > Thanks > > > > Sunny > > > > > On Jun 24, 4:49 pm, StrongSteve <swe.sta...@gmail.com> wrote: > > > > > Hi Sunny, > > > > > > You need some kind of polling solution. > > > > > > For example an invisible frame on the client side that asks the server > > > > > periodically (f.e. every second) if the session is still valid. > > > > > If not, then this invisible frame will display an alert box on the > > > > > client side informing about the session expiration. > > > > > > Greetings > > > > > Stefan > > > > > > On 24 Jun., 12:02, CIAO <pratik.sachd...@gmail.com> wrote: > > > > > > > Hi, > > > > > > What i am trying to do is that I have created a simple login page > > > > > > through which user identifies himself, after successful > > > > > > authentication > > > > > > of the user as soon as he enters the data page a cookie is created > > > > > > on > > > > > > the client side with a session name string in it also the same > > > > > > session > > > > > > name and the time of creation of the session gets stored in a > > > > > > Hash-map > > > > > > on the server side say if user does not logs out then his session > > > > > > continues to persists till the session is timed out. Also at the > > > > > > time > > > > > > of session expiry the cookie gets deleted and the value from the > > > > > > Hash- > > > > > > map is removed by a timer task running on the server side. thereby > > > > > > removing all the information about that session from the application > > > > > > > Now the problem is Say that user has opened a window (Session) and > > > > > > has > > > > > > forgotten about it then he will remains logged in (Till he > > > > > > refreshes/ > > > > > > Closes the browser/Sign-out) in-spite of the fact that his session > > > > > > has > > > > > > expired. > > > > > > What i want to do is that as soon as the timer task discovers that > > > > > > the > > > > > > session has expired it should send the user information that "your > > > > > > session has expired" and log him out automatically. > > > > > > > mind that the hash-map used is a static map and its method for > > > > > > inserting the values has been kept as synchronous to cater to > > > > > > different browser/Systems > > > > > > > Thanks in Advance > > > > > > Sunny > > > > > -- > > > > 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-tool...@googlegroups.com. > > > > To unsubscribe from this group, send email to > > > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2Bunsubs > > > > cr...@googlegroups.com> > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > SessionTimeOutControl.java > > > 6KAnzeigenHerunterladen -- 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-tool...@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.
