Region Domain

How the region domain looks like

A Region domains handles everything related to regions. The internal architecture is basically the same for Agent Domains.

Region Services

Region Services handle stateless information about regions. This can be name, parcel information and so on. This can be cached and can be public.

Region Hosts

These are the things we know today as simulators. They handle all the in-world interaction between objects and avatars. They rely on Region Stores to obtain their data (be it parcel information, objects in the region and so on). Is a Region Host down, the region it simulated is not available.

Region Stores

Region Stores hold the actual data about a region. This can be objects and their position, parcel information and so on.

Other Region parts

There are some further services needed which e.g. map the IP address of an in-world object.

How login works (part 2)

After the login in the Agent Domain has taken place, the process goes on with the login in the Region Domain.

1. agent host contacts region service
2. region service queries region store to obtain information about the region
3. region service contacts region host to ask it to establish a session for the new agent
4. agent host put in direct contact with region host (e.g. for getting the avatar)
5. agent host returns region host to viewer (for direct communication)
6. viewer now can talk to correct region host

Now this actually means that the Viewer itself does not decide to which region to connect. Or it might be part of the information send to the Agent Service in step 1 of the agent domain login process.