Handling broken connections

[Niksac]

I'm testing with latest peerjs and two latest version chrome browsers.

When i connect two peers using peerjs and then shutdown the network, the connection "close" event does not fire.

The connection's readyState stays OPEN and I do not notice the disconnect in code.
The connection will not recover when I restore the network.
I get a "close event" after something like 10 minutes and only as a result of using send() on the connection.

The peerjs control connection fires its handlers much faster.

My question is: how to handle such disconnects. Do I need to implement my own kind of heartbeat between the clients?
Can i utilize the websocket's "ping" functionality for that or is there an even better way?

[newelement]

I have the same question, but in my situation it is using the navigator.mediaDevices.getDisplayMedia. When the browser's dialog opens to allow a user to close the screen share it is the same as @Niksac mentioned. It does not fire a close event thus locking up all other peers with a frozen frame from the screen share.

[DirkHeinke]

I'm wondering if a better heartbeat should be in the library or if everyone program should have its own implementation. Did you solve your problem @Niksac?

[Niksac]

@DirkHeinke no, it's still on my "to fix" list.
A heartbeat in the library would definitely be cool for people not as knowledgeable in socket stuff (like me).