<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Read the thread 'a modest proposal' in the archives for more info about agents and regions - and please add that info to the wiki.<BR>
<BR>
/Stefan<BR><BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> From: tleiades@hotmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Date: Sun, 14 Oct 2007 13:07:31 +0200<BR>> Subject: Re: [Opensim-dev] users and agents table, and other oddities?<BR>> <BR>> > But yeah I think there is a lot of confusion about the UserAgent thing in <BR>> > the user server. I know I got a bit confused about that just last week. It <BR>> > seems that the UserAgent in there is really more of a UserSession, ie a <BR>> > new UserAgent is created every time the user logs in.<BR>> <BR>> Let me try to come up with a few definitions of terms, which doesn't require <BR>> a lot of refactoring:<BR>> <BR>> Sim/Simulator: a program which runs a simulation of objects interacting, <BR>> possibly with the involvement of simulated physics.<BR>> <BR>> Region: a 256x256 wide area, having a terrain and a number of objects, <BR>> interacting<BR>> <BR>> A Sim can house multiple regions, and each region can house multiple objects<BR>> <BR>> An object can either be a collection of prims or an avatar<BR>> <BR>> User: This represents a person in the real world, somthing which has an <BR>> email, a username etc.<BR>> <BR>> Viewer: an application which is used to view the state of the simulation. <BR>> Currently I know of three, the LL viewer, the OpenSL test client and <BR>> AjaxLife<BR>> <BR>> Agent: in a way, this can be thought of as a cursor, indicating what <BR>> position inside the simulator, the viewer is observing from., typically a <BR>> viewer will have multiple agents, a primary, often backed by an avatar, and <BR>> multiple child agents, in the neighboring regions.<BR>> <BR>> Session: Each connection between a viewer and an agent, regardless if the <BR>> agent is the primary or one of the child agents. Personally I would prefer <BR>> that we named child agents as sub-agents, and the sessions between the <BR>> viewer and sub-agents as sub-sessions.<BR>> <BR>> Unless somebody strongly objects to this convetion, I will start using that <BR>> naming convention in my codewriting.<BR>> <BR>> > One thing that we have repeatedly said is that we need to rewrite all the <BR>> > backend servers (ie user server etc) as the current ones are the result of <BR>> > very early work, from before we really knew how a lot of things worked or <BR>> > would work. One of the goals of 0.5 is meant to be that rewrite of the <BR>> > servers and the protocol between them and the regions.<BR>> <BR>> won't that hurt the goal of "frequent releases" ?<BR>> /tleiades<BR>> <BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>