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
A javascript nodejs client connected to a local websockets tokel daemon node does not properly disconnect:
after client end getwspeers still shows the js client in the list
daemon console shows a error: [info] Error getting remote endpoint: system:22 (Invalid argument)
This does not happen when a client disconnects from a remote linux daemon
Also a js client disconnects okay from a non-ws daemon node.
That is, the issue is possibly in websocketspp lib or its usage by the daemon code
Currently disconnect in js is done by a call to socket.end() and there is an event to catch 'close' (so it is not an early client app finish). I also tried to use socket.socket.close() call for the js websocket object but this also did not help
The text was updated successfully, but these errors were encountered:
dimxy
changed the title
tokel, websockets support, websocket.end does not disconnect from localhost ws node
tokel with websockets support: js client does not disconnect from localhost ws node
Jul 4, 2022
A javascript nodejs client connected to a local websockets tokel daemon node does not properly disconnect:
after client end getwspeers still shows the js client in the list
daemon console shows a error: [info] Error getting remote endpoint: system:22 (Invalid argument)
This does not happen when a client disconnects from a remote linux daemon
Also a js client disconnects okay from a non-ws daemon node.
That is, the issue is possibly in websocketspp lib or its usage by the daemon code
Currently disconnect in js is done by a call to socket.end() and there is an event to catch 'close' (so it is not an early client app finish). I also tried to use socket.socket.close() call for the js websocket object but this also did not help
The text was updated successfully, but these errors were encountered: