Refactor redundancy and load balancing

[mike]

Seems like the redundancy / load balancing code could be refactored so that it isn't repeated each time it is used (i.e. Realm Server, Directory Server, Simulation Server)

[mike]

Milestone beta-test deleted

[mike]

Created branch /branches/211-refactorha

[mike]

Requirements: There should be no single point of failure for any service MV3D provides and that servers below the Directory servers can come and go with little disruption. Starting at the top, a Directory should be split horizontally (by item id) across a number of servers. Each part of the Directory should be replicated to several servers. Asset Groups and Realms should get the same treatment. Realms should organically divide items across Simulation Services based on the Area they are in. All Items should exist on at least two Simulation Services. To further complicate things, some types of Areas can spread themselves across multiple servers, which means the objects within them have to do the same. It is very important to keep objects in the same Area (or piece of an area) on the same server so that there is no time lag for physics collisions.

[mike]

See also: journal post

[mike]

Created #343, #344, #345, #346 to integrate the new functionality.

[mike]

Trunked in [846]