I am developing a flex application using BlazeDS on Tomcat. I am trying to make the application automatically handle server session timeouts. That is, if the server session times-out, the next communication from the client to the server will create a new session.
I am using RemoteObject and can easily capture the "Client.Authentication" fault that is thrown as a result of a call if the server has already timed-out. I can easily log back in following this fault. However, I don't know how to resend the failed call. Does anyone have any suggestions on how to resend the failed call or how to detect the timeout before I actually make the call? I have considered doing a simple no-op call to verify the connection before each RemoteObject call, but that seems very inefficient to me. I know I can turn off the server-site timeouts as well, but I don't really want to have a lot of unused sessions hanging around. Thanks for any help. - David.
