If the user scrolls the view, then an update should be sent to the server
Requirements:
- 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)
- 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.