> Here's a good reason for each client to know it's session status
> (connected/disconnected/expired). Depending on the application, if L does
> not have a connected session to the ensemble it may need to be careful how
> it acts.
connected/disconnected events are given out in the current API but when I
shutdown the full ensemble I don't receive a session expired.
I'm considering implementing my own session expiration by tracking how long
I've been disconnected.
Location: San Francisco, CA