The session interface has the method invalidate() in it to manually force the session to expire. You can add some sort of filter in your server side RPC processes that uses whatever heuristic you need to determine when to time out the session and just do it manually.
On Jun 16, 8:34 am, Paul Grenyer <paul.gren...@gmail.com> wrote: > Hi All > > We have an application that makes regular RPC calls, on a timer, to > the client. This has the side effect of the user's session never > expiring. Because of the sensitive nature of the data we're handling > in our application, we need the user's session to timeout. > > How can this be done? > > -- > Thanks > Paul > > Paul Grenyer > e: paul.gren...@gmail.com > b: paulgrenyer.blogspot.com -- 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.
