Closed kendo55 closed 1 year ago
Hi @kendo55
If I start the WSClient.py agin, the WS-serverlog display "connect". Unfortuanaly it takes a new Id (2). the third time it takes a new Id (3) a.s.o.
Don't you see that's the correct way to do by using new ClientID when previous Client disconnects and new Client connects ? I'm closing this non-sense issue, and won't open until you prove it a real bug of the library.
Describe the bug
i tested the the WS connection in the AsyncFSWebServer example. As client I use your WSClient.py If I kill the connection, the WS-serverlog display "disconnect". Thats o.k. If I start the WSClient.py agin, the WS-serverlog display "connect". Unfortuanaly it takes a new Id (2). the third time it takes a new Id (3) a.s.o.
Debug log
I tried to add client->close(1) in the void onWsEvent()
but in the "AsyncWebSocketClient::close" you have if (_status != WS_CONNECTED) return; and the Queue-Entry will not by deleted