<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>We actually already do this on an intranet conferencing installation connected to a community.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Tue, 4 Nov 2008 08:25:57 -0500<BR>> From: jamesh@bluewallgroup.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] User vs Avatar [WAS: Proposed additional db fields]<BR>> <BR>> Stefan Andersson wrote:<BR>> > It is my firm belief, based on numerous integrations with custom<BR>> > backends, that we should separate the 'user' concept from the 'avatar'<BR>> > concept. On all Tribal Medias productions, the user logs on with a<BR>> > user id, not avatar first/last. In the real world (aka non-sl-grid<BR>> > world) it makes sense to separate them in the db.<BR>> > <BR>> > Maybe the cross-section would be the 'agent' - and in the simplest of<BR>> > instances, agentId == userId == avatarId.<BR>> > <BR>> > What I mean is that an asset was uploaded and accessed by an 'agent',<BR>> > not a 'user' or an 'avatar'. This should be reflected in the tables as<BR>> > well.<BR>> ><BR>> I think this would be great. Avatar name collisions wouldn't matter<BR>> anymore. So, users wanting to use their real names would be able to, and<BR>> inter-grid travel would be easier w/o the avatar name collisions.<BR>> <BR>> <j> BlueWall<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>