Hi Ryan!
Until now I've just played around with the WebSocketClient included in
Grizzly's 2.1.8 WebSocket API. So, it's the websocket version that the
WebSocketClient class is using.
I haven't used a brower yet.
The question is:
Does Grizzly's WebSocket implementation perform any connection
maintainance / heart-beating under the hood or do I have to implement
the logic by myself?
Best regards,
Phil