It does not automatically ping the remote end. You'll have to add
that to your client code. Or start a new thread on the server to ping
and respond properly. On the server end we rely on detecting dropped
connections to clean up dead connections.
On Mon, Jan 9, 2012 at 10:19 AM, <justphilmusic_at_googlemail.com> wrote:
> 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
--
You can find me on the net at:
http://antwerkz.com
http://antwerkz.com/+
http://antwerkz.com/linkedin
http://antwerkz.com/twitter