Alternative to session keep-alive

[Ben Mark]

Hi there Janusers,

We recently migrated to using reactive streams in our signalling server.

this means that whenever a socket connection goes down, we get that event immediately without sending keep allives every scheduled second.

 

My question is:

Is it reasonable or sounds logic to any of you, to dispose the session via incoming browser events  instead of communicating with janus on every single client 

by sending on each client's stream id a keep alive payload?

Its possible with reactive streams:

to catch any browser closed/refreshed etc.. without sending every few seconds "keep alive"

Suggested way of implementation:

to set sessionTimeout to infinite and to dispose the session via

reactive events which are resilient and reliable (tested them for nearly a month now)

would be more than glad to hear your opinions on this one.

~Ben

[Lorenzo Miniero]

Janus is transport agnostic, it's not just HTTP, so we need an application level keepalive. You may be able to detect disconnections reliably on the client side, but the keepalive is needed by *Janus* to figure out you're gone: if your laptop falls into the pool, you won't be able to tell Janus you're gone, it will need to figure it out by itself. That said, you're free to set the session timeout to 0 and disable it, if you think you don't need it.

Lorenzo