My guess is this is highly unlikely to work consistently if at all. We simply have our session timeout short enough that the session will not be 'orphaned' very long. In the client app, we put in a 'keep alive' call to 'something' on the server on a timer shorter than the session timeout. If this call fails, it tries again several times more quickly before warning the user that the server session may have timed out or something.
Not sure if this is a great idea but I'd love to hear any other suggestions on this one. - Todd --- In [email protected], "meteatamel" <[EMAIL PROTECTED]> wrote: > > I'd try onunload and onbeforeunload events to see they help. If that > doesn't help, I'd try putting up an Alert box before making the AMF > call to make sure AMF call is made before the browser is closed. > > -Mete > > --- In [email protected], "Dan" <yldleung@> wrote: > > > > Hi, > > > > I am trying to invalidate a session by explicity invoke a AMF call > > when the user click logout or closing the browswer. > > > > By ExternalInterface, the CLOSE event is capture within the FLEX > > correctly. But by tracing in the debugger, if a AMF is invoke upon > > this, the call did invoke but the AMF call is not sent to through the > > FDS, I wonder if the application is being killed before the FDS > > successfully sent the request. > > > > Is it not a good idea to invalidate a session in this way? Any > > Flexpert suggestion? :> > > > > Dan > > >
