Proposal: P2P server architecture

[Neekhaulas]

WIP

I'm working on the Lobby architecture and there is the need to define how the structure will work. Actually the architecture is only a simple server/client but we will go to an P2P system.

My proposal is to build it like this : https://leaguesandbox.github.io/media/networking-phase-5.png

These are the different people :

• Master Lobby Server host : they will host a script that create nodes with P2P to not have a centralized server
• Lobby Server host : they will host server that can run games
• Lobby Client user : they will use the lobby client

And here how the protocol would be :

• As Master Lobby Server host, I want people to connect on the server thanks to the P2P system
• As Master Lobby Server host, I want that my Master Lobby Server have the same state that everyone else
• As Lobby Server host, I want to be able to password protect my Lobby Server
• As Lobby Server host, I want to be able to hide my Lobby Server
• As Lobby Server host, I want to be able to set the number max on running game on the server
• As Lobby Client user, I want to be able to see the quality of a Lobby Server
• As Lobby Client user, I want to be able to rate the quality of a Lobby Server
• As Lobby Client user, I want to be able to see the ping of a Lobby Server

[JakeFromStateCS]

What if we offer both P2P or local servers as well as ones on a main server? Similar to how you can create dedicated source servers, but still host listen servers.