Bastian Kersting
Bastian Kersting
In software, nothing happens without any reason. The nodejs implementation contains logic for reconnecting when the underlying websocket connection is closed for some reason (laggy network or whatever). This implementation...
This behaviour is now different with #229, this won't panic but rather try to reconnect on a transport error. I am closing this bug as it is outdated.
Hi @WildEgo, nice that you're interested in the library! Until now I didn't find the time for adding that example (that's why I also added the `good first issue` label...
Great! I appreciate the help!
Implemented in #229.
Can you further elaborate on this feature?
Yes, just opened it!
I would honestly prefer the former, as it sticks more to the socketio API. Also the latter could be more difficult when reacting to a custom event. And I honestly...
With 0.4.0 being about reconnect refactor, we should either rename this to 0.5.0 or close.
Hei @nshaaban-cPacket this sounds great! I think a server implementation is definitely the most needed feature for this crate. I think the basic requirements are a full match of what...