On 1/9/12 7: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.
To go back to your original question, I've locally tested that pings are
responded to automatically, however, I'm making some changes to
make sending pings a little more straight forward.
Can you share your code? Would like to see what you're doing different.
>
> 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?
At this point, there is no heart-beat feature. However, it probably
wouldn't
be a bad feature to offer. I would recommend logging a feature request.
>
>
> Best regards,
> Phil