When you unplug the network cable the client may not get a disconnect event from the networking layer until it tries to use that connection to send a request to the server. You might need a "heartbeat" ping which runs periodically to test the connection to force that close event.
Also, if you are on 2.5.1 you might need a hotfix as there was a bug where a client who disconnects, then reconnects again immediately before the session expires was not getting resubscribed properly. That is fixed in 2.6 and 2.6.1. Jeff From: [email protected] [mailto:[email protected]] On Behalf Of Besite - Bart Sent: Thursday, December 11, 2008 9:36 AM To: [email protected] Subject: Re: [flexcoders] LCDS - Handling client disconnection on the server Hi Jeff, I wil have a look at Seth's blog. This morning I tried the following : I have my Data Management Service. On the server I have an assember extending the AbstractAssembler and implementing the MessageClient interface. I bound messageClientCreated and messageClientDestroyed listeners to this class. This works fine and the messageClientDestroyed gets called when I log out or close my browser, but it is not called when I plug out my utp cable... do you know the solution for this ? Thanks in advance, Bart On the server, you can listen for session disconnect events. Probably the best intro to this is Seth's blog posting: http://greetingsfromoakland.blogspot.com/2008/11/post-max.html Jeff From: [email protected] [mailto:[email protected]] On Behalf Of Besite - Bart Sent: Thursday, December 11, 2008 7:33 AM To: [email protected] Subject: [flexcoders] LCDS - Handling client disconnection on the server Hi, I have a Data Management Service running on my Livecycle server. I have a managed array collection of Users. When a client disconnects (he closes the application or his browser or his internet connexion is lost), I want the client's user to be removed from the managed array collection of Users. Is there a reliable way for the server to detect that a client is disconnected ? I don't want to rely on the Application.onDisconnect event of the Flex application... Kind regards, Bart
<<inline: image001.jpg>>
<<inline: image002.jpg>>
