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 guess it is pretty obvious that every beginning needs an ending, specially when you use asynchronous tcp socket.
in my case i need to :
connect to a web socket server
send/receive data
close the connection
when you see a begin() method you expect an end() method as well.
after calling the disconnect() method, the socket wont get destroyed, it remains there and it tries to reconnect to the server!
and every time i connect to the server for a new session i get n + 1 client sockets because the previous one is still there.
the only work around the issue, at least what i could think of is to destroy the webSocketClient object manually and create a new one when i need it .
The text was updated successfully, but these errors were encountered:
hello
i guess it is pretty obvious that every beginning needs an ending, specially when you use asynchronous tcp socket.
in my case i need to :
when you see a
begin()
method you expect anend()
method as well.after calling the
disconnect()
method, the socket wont get destroyed, it remains there and it tries to reconnect to the server!and every time i connect to the server for a new session i get
n + 1
client sockets because the previous one is still there.the only work around the issue, at least what i could think of is to destroy the
webSocketClient
object manually and create a new one when i need it .The text was updated successfully, but these errors were encountered: