Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Platform implement #301

Open
PhuNguyen182 opened this issue Jun 14, 2024 · 1 comment
Open

Platform implement #301

PhuNguyen182 opened this issue Jun 14, 2024 · 1 comment

Comments

@PhuNguyen182
Copy link

Can MemoryPack work well on mobile platforms such as Android, iOS, or WebGL platform?

@PhuNguyen182 PhuNguyen182 changed the title Platform execution Platform implement Jun 14, 2024
@danfma
Copy link

danfma commented Jul 19, 2024

We use this communication method in a game to connect our clients and servers. We have a Unity client for Android, iOS, and WebGL connected via WebSockets. Additionally, we have a Blazor WebGL app that communicates using the same shared library used by Unity with our .NET server.

We have added the MemoryPack formatter support for our endpoints, so all serialization is performed using JSON or the memory pack, which works pretty well.

It's important to note that the payload may not always be smaller than JSON + compression (GZIP, Brotli, etc). However, if your server can generate the serialized data with minimal resources and the payload is small enough (the case when using MemoryPack), it's a good trade-off. Also, you can enable compression, but in our case, it wasn't necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants