3 ms·
Got it... I'm not sure I understand the use case for this tool then? In a browser, the TCP connection will close itself. On a mobile device, the TCP connection
by tylermauthe 12y ago
Got it... I'm not sure I understand the use case for this tool then?
In a browser, the TCP connection will close itself. On a mobile device, the TCP connection will close when the network connection drops.
I suppose a server could reliably keep a TCP connection open, but at that point why wouldn't I just deal with the messages myself..?
- dropfrog 12y agoMobile device connections work well enough -- a reliable VOIP app on Android was constructed with the DropFrog service on the backend. Generally, a network connection can get dropped on any device even for a "server" device; it is a failure case to anticipate and program accordingly. On DropFrog, by the way, the channel continues to exist if there are any participants and also for half a minute with no participants whatsoever, anticipating and accommodating failure cases. For the browser (and more) consideration, WebSockets under control of the application programmer makes the most sense, fulfilling the requirements of a persistent and secure connection (WSS). WebSocket support will be added in the future.
- tylermauthe 12y agoAwesome! Thanks for the info. Good luck with the product, hope to find some time soon to try it out.