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
I made initial implementation of the websocket callbag. The problem I encountered is: how to tell the user that WebSocket is connected. So far I implemented buffer that stores the data that should be sent to the WebSocket connection, but I believe that information about successful connection is way too important to hide it inside callbag.
I checked WebsocketSubject from RxJs, and they allow to pass openedObervable in the config, that stores connection state.
The text was updated successfully, but these errors were encountered:
I made initial implementation of the websocket callbag. The problem I encountered is: how to tell the user that WebSocket is connected. So far I implemented buffer that stores the data that should be sent to the WebSocket connection, but I believe that information about successful connection is way too important to hide it inside callbag.
I checked
WebsocketSubject
from RxJs, and they allow to passopenedObervable
in the config, that stores connection state.The text was updated successfully, but these errors were encountered: