Add a WebSocketChannel.ready field about web_socket_channel HOT 18 CLOSED

Looks like authors of this library never developed a real world application (it works on my system syndrome). Seriously, I am amazed that this issue is now open since mid 2018 and being tossed around the park. Currently upon first connect, there is simply no way to know if/when the connection is ready.

How do you even build a real world app with this?

from web_socket_channel.

Maybe it will help today to know that the socket is connected and close

connection() async {
    WebSocket ws = await WebSocket.connect('ws://echo.websocket.org');
    print('ws open');
    ws.listen(
      (data) {
        print(data);
      },
      onDone: () {
        ws.close();
        print('ws close onDone');
      },
      onError: (error) {
        ws.close();
        print('ws close error = $error');
      },
    );
    IOWebSocketChannel iows = IOWebSocketChannel(ws);
    iows.sink.add(('Hello, World!'));
  }

from web_socket_channel.

I'm no longer on the Dart team, so I'm not involved in the maintenance of this package anymore.

from web_socket_channel.

@nex3 hi!
please tell us, any updates on a this problem?

from web_socket_channel.

@nex3 Can you mention the person who is currently involved in maintenance of this package? Because issue (depending issues) is real and here for a long time. thanks!

from web_socket_channel.

I'm not sure who's maintaining it these days. Judging by the lack of movement on this issue and the pull requests, it may be no one.

from web_socket_channel.

@nex3 @nailgilaziev I have added such field and made a PR. Not sure if it's the cleanest solution (probably not since I am a newbie when it comes to Dart) but maybe someone wants to take a look and improve it there is anything to improve.

from web_socket_channel.

hello , is there any one working on this ?

from web_socket_channel.

Any working solution on this? I can't detect the connection state from IOWebSocketChannel object.

from web_socket_channel.

This would be a useful feature for users who are somewhat new to Websockets.

from web_socket_channel.

If you work with IO my workaround of this issue is to listen to inner websocket state, but it's ugly method and I will rewrite this appoach lated:

    _quoteSocketChannel = IOWebSocketChannel.connect(
      Uri.parse(SubscriptionEndpoint(token: jwt).path),
    );
    _quoteSocketChannel.stream.listen(logger.i);


    Timer.periodic(Duration(milliseconds: 200), (timer) {
      if (_quoteSocketChannel.innerWebSocket?.readyState == WebSocket.open) {
        timer.cancel();

        _quoteSocketChannel.stream.listen((message) {
          print(message);
        });

from web_socket_channel.

I'm encountering this issue as well. Not a lot of good options to get around this.

from web_socket_channel.

Is it really that hard to add a connection state stream?

from web_socket_channel.

cc @kevmoo Kevin can you help us to triage this?

from web_socket_channel.

@brianquinlan @devoncarew – thoughts?

from web_socket_channel.

Yo guys
I have a retrytTimer in onError and onDone, otherwise it is set to null
You just need to check if the retryTimer is null. That's all

from web_socket_channel.

I plan on reviewing #240

Could anyone who has an opinion about this feature please take a look?

from web_socket_channel.

For others who have subscribed to this issue:
It seems like this was "silently" implemented by #240.

from web_socket_channel.