Implement a binary protocol instead of sending JSON over WebSockets #103

New issue

Open

opened 2024-09-20 21:03:03 +02:00 by riki · 0 comments

riki commented

2024-09-20 21:03:03 +02:00

Owner

With how frequently rkgk sends out events, using JSON is extremely inefficient. It would be healthier to implement a binary protocol that doesn't repeat names as often.

I say "implement" and not "use" because I'd like a lightweight, holistic solution that works well for our use case. For instance we don't need version compatibility, as the app refreshes for everyone once we upgrade the server, and then clients download the updated version.

On the Rust side, we'll probably implement a custom serializer/deserializer, and we'll also generate code to handle the binary magic on the JavaScript side.

With how frequently rkgk sends out events, using JSON is extremely inefficient. It would be healthier to implement a binary protocol that doesn't repeat names as often. I say "implement" and not "use" because I'd like a lightweight, holistic solution that works well for our use case. For instance we don't need version compatibility, as the app refreshes for everyone once we upgrade the server, and then clients download the updated version. On the Rust side, we'll probably implement a custom serializer/deserializer, and we'll also generate code to handle the binary magic on the JavaScript side.