Problem: Error is not thrown on WebSocket disconnect
Device: 15" MacBook Pro 2017
OS: macOS Catalina
Browser: Chrome v81
Misc: Turn is forced
As the Kinesis library sits on top of WebSockets it would be great if it could do a better job (than what is default behaviour) at handling connection loss. The only current way to monitor losing connection to Kinesis is to monitor peerConnection.connectionState. This is a tad tricky when you want disconnect and reconnect deliberately vs due to wifi conditions.
Use case: Going from one wifi network where Kinesis is allowed to another where it is blocked but IP whitelisted traffic is allowed (not possible with Kinesis). If I query myself or check for internet it will come back as a success yet I lost connection to Kinesis.
Useful link: https://stackoverflow.com/questions/26971026/handling-connection-loss-with-websockets
NB: This library is very helpful and I very much appreciate your work.
Problem: Error is not thrown on WebSocket disconnect
Device: 15" MacBook Pro 2017
OS: macOS Catalina
Browser: Chrome v81
Misc: Turn is forced
As the Kinesis library sits on top of WebSockets it would be great if it could do a better job (than what is default behaviour) at handling connection loss. The only current way to monitor losing connection to Kinesis is to monitor peerConnection.connectionState. This is a tad tricky when you want disconnect and reconnect deliberately vs due to wifi conditions.
Use case: Going from one wifi network where Kinesis is allowed to another where it is blocked but IP whitelisted traffic is allowed (not possible with Kinesis). If I query myself or check for internet it will come back as a success yet I lost connection to Kinesis.
Useful link: https://stackoverflow.com/questions/26971026/handling-connection-loss-with-websockets
NB: This library is very helpful and I very much appreciate your work.