Clients register for updates at the server. What does this mean? Whenever the player is looking at a piece of the map, the client says "I'm looking at the region from (x, y) to (x', y')." The server will then send updates to that client, whenever something changes in the given region.
If the user scrolls the view, then an update should be sent to the server
- Registrations must be uniquely identifyable.
- The client must be able to update and delete a registration.
- Clients can have more than one registration.
- Whenever a piece of the map changes, the updates are sent to all clients that have registered that piece of the map.
- Updates are queued and sent in bulk. (this saves bandwith)
If I combine requirements 1, 2 and 3, then it could be wise to let the client create its own ID numbers for registration. Consequences:
- The server can uniquely identify a registration by the combination of the PlayerID of the client and the registration ID.
- Clients can assign registration ID's at will. They do not have to request unique ID's at the server. (i.e. it's faster)
- Clients assign registraion ID's to views and delete them whenever a view is closed.
_________________Feel free to contact me over Email! My current timezone: Europe/Amsterdam (GMT+1 or GMT+2)
[ General TE Discussion ] [ TE Development ] [ TE Coding ]
| Transport Empire -> |