If you run the examples here https://github.com/socketry/async-slack/tree/master/examples/alive
Using websocket ping/pong frames, the connection will terminate abruptly shortly after 3 minutes.
Using slack ping/pong messages, the connection will keep alive.
According to the documentation
Clients should try to quickly detect disconnections, even in idle periods, so that users can easily tell the difference between being disconnected and everyone being quiet. Not all web browsers support the WebSocket ping spec, so the RTM protocol also supports ping/pong messages.
I think either the documentation is unclear, or the implementation is broken somewhere.
cc @RodneyU215 and @Roach
If you run the examples here https://github.com/socketry/async-slack/tree/master/examples/alive
Using websocket ping/pong frames, the connection will terminate abruptly shortly after 3 minutes.
Using slack ping/pong messages, the connection will keep alive.
According to the documentation
I think either the documentation is unclear, or the implementation is broken somewhere.
cc @RodneyU215 and @Roach