Thanks, I basically got this working. The problem was that I had a thread running for each session that retreives their email periodically (not sure if this is a good idea). The session wouldn't destroy as long as the thread was running. To work around this, I basically have the server pinging the client registered with a session, if the client does not respond within 5 pings the thread is stopped - shortly after this the session is destroyed. I have a small number of users so this seems to work for now, i have a suspision this isnt the best way to do this but eh.
--- In [email protected], Seth Hodgson <[EMAIL PROTECTED]> wrote: > > http://livedocs.adobe.com/blazeds/1/blazeds_devguide/help.html? content=lcconnections_4.html#1076159 > > A browser closing has no immediate correlation to a server-side Http session being destroyed. Session destruction is generally based on a configurable timeout interval defined for the server (often in the range of 15 to 30 minutes). You can follow the advice in the docs above for notifying the server that the client has gone away and triggering session destruction in a near-real-time fashion. > > Also, registering for session creation notification is static, but registering for session destruction notification is per session instance. You can add your session destroy listener (generally the same impl class) from within your sessionCreated handler method. > > Seth > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of j301c > Sent: Wednesday, September 10, 2008 4:53 PM > To: [email protected] > Subject: [flexcoders] BlazeDS FlexSessionListener > > > Has anyone had any success with using the FlexSessionListener with > BlazeDS. My listener calls the sessionCreated method when the session > starts, but the sessionDestroyed method is never called when the user > closes the browser. Is this something only supported in Flex Data > Services? Any tips appreciated, thanks. >
