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

Handle Auth payloads > 500 bytes #148

Open
connorcarpenter opened this issue Mar 20, 2023 · 0 comments
Open

Handle Auth payloads > 500 bytes #148

connorcarpenter opened this issue Mar 20, 2023 · 0 comments
Labels
feature desired new functionality naia pertaining to naia crates

Comments

@connorcarpenter
Copy link
Member

Currently Auth payloads are restricted in size to ~500 bytes because the Server/Client handshake process is completely unreliable, and naia seeks to keep within a 500-byte limit for individual packets in order to avoid latency-increasing fragmentation. Normally users of naia can get around this limit with Reliable Message Channels, but Authentication messages don't currently support reliability.

My current reliable channel algorithm requires both Server & Client to agree on a starting message id .. I'll have to adapt this a bit in order to get reliability working before the connection is even established.

It's likely that this feature will wait to release with a greater refactor of the connection handshake process, which should, for WebRTC connections at least, authenticate the client during the HTTP session request rather than after the WebRTC connection is already established.

@connorcarpenter connorcarpenter added naia pertaining to naia crates feature desired new functionality labels Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature desired new functionality naia pertaining to naia crates
Projects
None yet
Development

No branches or pull requests

1 participant