AustinSmith13
commented
4 years ago I have determined that host migration is possible and is worth doing. We will have NAT punch through.
Implementation Details The host has a list of potential new hosts that considers play-time and connection. When the host disconnects, instead of immediately disconnecting it initiates a migration response to the players. All players are notified with the new host connection information. The new host is notified with the server side state.
Pros:
- Very little downtime, the host can still process events while it transfers ownership to the new host.
- No disconnect when a player host leaves. We can have the illusion that you can just create a world or drop a world that persists so long as there are people in it similar to other social games without the need of a large backend.
Cons
- The host player, when leaving the game to say another world or server. There might be an additional 5 seconds of overhead added to there loading time to that new world.
- If the host quits the application unexpectedly, all clients must disconnect. This is because clients do not know other clients IP address only the host does.
How to transfer the host?
Is this to much work than its worth?
Do we need to setup nat punch through.