Responding to ping event about web_socket_channel HOT 5 OPEN

And I have not seen anything related to how to send it from the client side either.

from web_socket_channel.

And I have not seen anything related to how to send it from the client side either.

You send it using the IOWebSocketChannel's pingInterval property:

 var channel =
      IOWebSocketChannel.connect('url_goes_here', pingInterval: Duration(seconds: 10));

The client will send a ping every 10 seconds, and wait for a 'pong' back from the server.

Documentation doesn't explain how to respond to ping event on server side.
ws.pong() and ws.send('pong) didn't work.

The library automatically responds to server ping events, no configuration is needed for that. It's part of the RFC 6455 spec.

from web_socket_channel.

Documentation doesn't explain how to respond to ping event on server side.
ws.pong() and ws.send('pong) didn't work.

The library automatically responds to server ping events, no configuration is needed for that. It's part of the RFC 6455 spec.

@mhstoller I am hoping you could shed some more light on the automatic response to server ping events.

We have a node WebSocket server that is using the RFC 6455 spec and sends a ping every 30 seconds to our flutter app.

The flutter app is connecting to the WebSocket server like this example below.

 var channel =
      IOWebSocketChannel.connect('url_goes_here', pingInterval: Duration(seconds: 15));

The server never receives a pong response and subsequently closes the WebSocket connection.

Can you point me to any documentation or where in the library the automatic response happens?

Should the server be expecting something besides pong in response?

from web_socket_channel.

@brax10ward so coming back to this a year later I don't want to dig through the code, but I did a cursory look and there's code like this:

case _WebSocketOpcode.PING:
            _eventSink!.add(_WebSocketPing());
            break;
          case _WebSocketOpcode.PONG:
            _eventSink!.add(_WebSocketPong());
            break;

I would guess that it responds to ping events with a ping of its own. With it being part of the spec though I would assume it's something that can be handled in the node library you are using without much work on your end.

That said, I was trying to set something similar up for my own connections and you can read what I ended up doing in the comments here: #124

from web_socket_channel.

I think that is transforming a Ping opcode on the wire into a Ping event in the application code.

The section we are looking for is
web_socket_impl.dart:L724

from web_socket_channel.