Fabian Hummel
Fabian Hummel
I have a similar issue with a rust server implementation (socketioxide) and socket.io-client. I am getting the error "got plaintext data when reconstructing a packet" in the socket.io-parser library. This...
5 years later and it still is not fixed. Why does the memory stay allocated after the connection is dropped? Any solutions?
Is it possible to work around this issue by using custom Middleware in axum or socketioxide to intercept the connection request and create a namespace with `io.ns(request.path /*target path to...
Using enums sounds good to me, especially because they are on the stack which is far bettern than trait objects. When people want to implement other parsers they could then...
I'll try to explain the issue I have been experiencing with socketioxide + socket.io-client. When sending two independent packets in a very tiny timeframe, they both arrive pretty much the...
The strict weak ordering is a relatively new addition to the standard library and could be the cause why I did not get this error some longer time ago. I...
If you mean the `useFn` parameter, yes, it would be better to change it to the context directly. Maybe allow for either of one, because I really like simply passing...
Implemented the aforementioned ideas and added tests + docs
Oh, I totally forgot about this option, I will implement it later that day, thanks!
I have a similar issue with a rust server implementation (socketioxide) and socket.io-client. I am getting the error "got plaintext data when reconstructing a packet" in the socket.io-parser library. This...