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

Protocol questions #9

Closed
jfrsmith opened this issue Mar 31, 2017 · 2 comments
Closed

Protocol questions #9

jfrsmith opened this issue Mar 31, 2017 · 2 comments

Comments

@jfrsmith
Copy link

I had a couple of questions about the protocol:

  1. How does it handle multiple clients behind a single IP address? The server protocol seems to ignore packets from a source address that it's already received a packet from, so this would suggest that it doesn't support this scenario.
  2. Do you have any ideas about how you'd implement parties? I.e. multiple clients wanting to connect to the same dedicated server? I'd imagine that you'd have to do a bulk request from either a party arbiter or a separate service, I'm assuming some kind of matchmaking service.

I like the sounds of the protocol, anyway! I'm interested in doing a full Rust implementation (I saw someone else has already jumped on that too :) ), so I'll see if I can bash away at it when I get some time.

Cheers,
Jack

@gafferongames
Copy link
Contributor

  1. It handles multiple clients behind and IP address with different ports. It only ignores packets if the IP:port combination matches an already connected client.

  2. No plan for parties right now, but I would suggest that you should be able to include information in the user data field of the connect token to describe the reservation within the existing 1.0 protocol.

Parties and reservations are a good extension for 1.1 that I'll consider. Thanks!

If you'd like to help out with the Rust implementation, all hands on deck, your help is welcome.

cheers

@gafferongames
Copy link
Contributor

ps. When I said address in the standard I meant address + port... updated the standard so it specifically mentions address + port in all instances.

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