I want to make sure all the server-side resources are being
cleared upon a Logout operation executed from a Flex application.
Also I want to handle the situation same thing happens server-side
when the user simply bypasses the Logout and kills their browser
window (so the connection with the FDS gets broken).
How to proper implement that on the server?
Trying to mimic the standard http "logout", I used
FlexContext.getFlexClient().invalidate(), but then I realized on
the next Login, FDS will reuse the same FlexClient object, which is
still in the invalidate state (??) hence all the operations
performed with it would fail. Should I try invalidating all the
associated FlexSession instead, so the FlexClient would get
automatically invalidated?
During normal client operation, FlexClient objects have
associated multiple FlexSession objects (http and rmtp). As
FlexSession can have associated multiple FlexClient and viceversa,
I am a bit confused on how to do the logout or handle a broken
connection, server side.
I'm working with the out-of-the box FDS configuration files,
the only things I added are destination definitions for mky Remote
Objects and Data Services.
Thank you.