Now that we've determined that sessions are what you need, let's understand how they are used in conjunction with deployments. We will use the same diagrams, while adding one principle at a time.
The sessions are an ephemeral entity which allows to manage the addition and the deletion of player or group of player on a deployment.
When you have a player who wants to connect to a game instance, you will create a session request to Arbitrium. Let's say there is already a deployment to host the session. We will see a little later than this can be automated.
This way, you can add multiple players in a single deployment. You can even add groups of players; just send their IP in the same session request.
We have now filled our deployment with players. However, player two must go to eat and leave the game. You just have to send us a request to delete the session corresponding to player two.
And now a new player can take his place with a new session request.
Now that you have a better understanding of what a session is, we will now look at how they work and some specifics.