You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happened to me: there were problems with the Internet on the client side, specifically the connection speed dropped significantly and at times the connection was completely broken, but briefly enough that the WebSocket connection was not closed. However, the problem is that the messages coming from the server were delivered in the wrong order. To be more precise, they all arrived at exactly the same time, so I think their order was mixed up, which caused a problem with the application. The WebSocket technology itself works based on TCP, which should guarantee the correct order of received messages, so it seems to me that the problem is with the WebSocket implementation in the Dart language, and more specifically with this library.
The text was updated successfully, but these errors were encountered:
This happened to me: there were problems with the Internet on the client side, specifically the connection speed dropped significantly and at times the connection was completely broken, but briefly enough that the WebSocket connection was not closed. However, the problem is that the messages coming from the server were delivered in the wrong order. To be more precise, they all arrived at exactly the same time, so I think their order was mixed up, which caused a problem with the application. The WebSocket technology itself works based on TCP, which should guarantee the correct order of received messages, so it seems to me that the problem is with the WebSocket implementation in the Dart language, and more specifically with this library.
The text was updated successfully, but these errors were encountered: