I’d like to know whether it’s possible to easily detect (on the server side) when Flex clients disconnect from a BlazeDS destination please? My scenario is simply that I’d like to try and use this to figure out how long each of my clients are connected for each session. I need to be able to differentiate between clients as well (ie so not just counting the number of currently connected clients which I see in ds-console).
Whilst I could program in a “I’m now logging out” process in my clients, I don’t know whether this will fire if the client simply navigates away to another web page rather than going though said logout process.
Can anyone suggest if there’s an easy way to do this type of monitoring on the server side please.
Many thanks,
Alex
The only way to do it right is to implement the heartbeat mechanism in a way or another. You can use the keep-alive from http coupled with session expire as suggested before but my opinion is to use the messaging mechanism from BlazeDS (send a message at X seconds). You can control the time interval and other aspects (maybe you want to detect if the client is not doing anything for several hours and to invalidate the session even if your client is still connected).
If you want to be notified instantly (chat application) when a client is disconnecting a solution is to have a socket (RTMP) or some emulation (http streaming) which will detect instantly if the client is disconnected, however this disconnection can be temporary (maybe the network was down for one second, and after that is ok, and you should also detect that).