Adrian Busse

Hey @googollee / @erkie / @mrfoe7, i am using go-socket.io in our backend application and would love to help maintain/update the project. The next few weeks will be pretty busy...

I'll look into it and update the examples/docs later this week.

Not easy to implement, because of how the encoding works into an engine io payload and the fact that JavaScript actually uses UTF-16 encoding for strings. I've got it working...

Yeah, this happens when you have raw utf-8 data.

@erkie The biggest problem is actually that JavaScript uses UTF-16 and engine.io payloads contain the data size. Decoding: https://github.com/adrianmxb/goseio/blob/4ea3bf17ed72b00181159f19f1ff7d01d8f92973/pkg/eio/parser/parser.go#L123-L184 Encoding: https://github.com/adrianmxb/goseio/blob/4ea3bf17ed72b00181159f19f1ff7d01d8f92973/pkg/eio/parser/parser.go#L74-L90 I built a small proof of concept library that...

I am not really a fan of the default room solution either. This library is far from the standard in some regards already and it will get harder and harder...

The issue is that the length parameter sent by the javascript client isn't compatible to the server parser. Javascript uses UTF-16 for its strings internally which causes this. I started...

can you post your client code / tell us the version of the client library you used?

I could be wrong but as far as I know there is currently no way to do this. Should be pretty easy to add though. Check out https://github.com/googollee/go-engine.io and feel...

Just to bump this again, I don't see anything blocking the PR as it basically just implements a decorator for new [validator.js](https://github.com/validatorjs/validator.js/) functionality. Can we maybe get this released soonish?...