Jun 16, 2020, 5:28:56 AM6/16/20
we're experiencing a problem dealing with comet sessions when a user reloads the application page.
We identify users by a key value. When a user reloads the web page, an onBeforeUnload handler disconnects the comet session. When the page then loads up again, a new comet session is established with the same user key value. Server-side, before handing control of the user to the new comet session, we check that there's no previously active session (for the same user key) still connected.
On some browsers, the onBeforeUnload handler does not fire properly or completely (namely, Firefox),
so the corresponding comet session results still active when the new one tries to take control.
I was wondering if anyone using comet has had to deal with this problem and how they've done that.