Graceful handling of server timeout in BlazeDS
- by Rydell
I have a flex client that makes service calls to a tomcat server running BlazeDS. I would like to gracefully handle server session timeouts in this environment.
I do have security constraints on the service, so the client authenticates against a remote object by initializing a ChannelSet based on the destination, and then logging in using that ChannelSet.
After the user is authenticated, if they go get a (long) cup of coffee, their session will inevitably time out.
I would like the client to detect the timeout, and return the user back to the login page, with the appropriate informational messages.
But I am having difficulty finding the best way to detect this timeout from the client. Is it possible, or must I have the server throw an error when the timeout occurs?
Thanks!