[Opensim-dev] Client Serialization and Transfer between Regions!

[Justin Clark-Casey]

On 11/04/11 20:39, Umar Farooq wrote:
> Hi Dear,
>
> Thanks for the previous help! Now, I am in a position to create a new
> region on a remote system and now working to transfer the client from a
> region to the newly generated region. I have a bit of confusion here in
> Client and Agent, that are clearly defined in the wiki. In some older work
> to get circuitcode it is referred to a client through ClientManager of a
> scene object. I can see that there is a change in the code now, I been
> through the serializable class for agentCiruitData, which I am assuming is
> the replacement to get serialization for a client data.

Client refers to the viewer as a whole.  An agent is an agent of the client in a particular region of a particular 
simulator.  Each agent has a separate network connection (circuit) with the client.

Agents can be root agents or child agents.  A root agent exists in the sim that the client's avatar is in.  A lot of the 
interaction with the simulator flows through this root agent.

Child agents existing on neighbouring regions and send back information about events on those regions - this is why the 
viewer can 'see' into those regions even though they might be hosted on remote servers.

AgentCircuitData does hold connection information.  ClientManager is probably a name from the old days.

>
> I am asking for some guidance if I am looking into the right place at this
> point. I was thinking to see how the teleport mechanism is working which
> might give me an idea. I am sorry, if asking something too stupid. Thanks
> again! Need guidance in a correct direction.

The bulk of the code for the teleport mechanism is in 
OpenSim/Region/CoreModules/Framework/EntityTransfer/EntityTransferModule.  It is involved and complicated so will 
probably require a large amount of study.  Unfortunately, I don't know of any place where the teleport mechanism is 
documented at a higher level.

-- 
Justin Clark-Casey (justincc)
http://justincc.org/blog
http://twitter.com/justincc