<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>Not fully groking you, but I would say that we would come a long step if we made sure all data sources were abstracted by a provider, so for example user profiles had its own provider, search had its et c.<BR>
<BR>
Remember, any given class (like a local user service proxy) can implement several provider interfaces, and thusly serve multiple roles - there's no real penalty to let separate context use separate interfaces to the same class, but it opens up for redirection and customization.<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=EC_stopSpelling>
<BR>
From: adam@deepthink.com.au<BR>To: opensim-dev@lists.berlios.de<BR>Date: Tue, 4 Nov 2008 04:58:12 -0500<BR>Subject: Re: [Opensim-dev] User vs Avatar [WAS: Proposed additional db fields]<BR><BR><BR>
<META content="Microsoft SafeHTML" name=Generator>
<STYLE>
.ExternalClass .EC_shape
{;}
</STYLE>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass p
{margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:'Times New Roman','serif';}
.ExternalClass tt
{font-family:'Courier New';}
.ExternalClass span.EC_EmailStyle19
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .EC_MsoChpDefault
{;}
@page Section1
{size:612.0pt 792.0pt;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">I’d love to have a DB pattern which better supported metadata myself.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">There’s been several occasions right now where it would have been handy to attach extra fields of data in (even if they cant be searched on easily).</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Adam</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=EC_MsoNormal><B><SPAN lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN lang=EN-US style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> opensim-dev-bounces@lists.berlios.de [mailto:opensim-dev-bounces@lists.berlios.de] <B>On Behalf Of </B>Michael Wright<BR><B>Sent:</B> Tuesday, 4 November 2008 1:38 AM<BR><B>To:</B> opensim-dev@lists.berlios.de<BR><B>Subject:</B> Re: [Opensim-dev] User vs Avatar [WAS: Proposed additional db fields]</SPAN></P></DIV></DIV>
<P class=EC_MsoNormal> </P>
<P class=EC_MsoNormal>I agree with Stefan, we have too much data mixed together in the dbs. Avatar appearance for instance. I don't believe that should be part of user data. We should either have it as part of the Inventory/Asset data or a separate Avatar data set. <BR><BR>Mixing all the data together like we do, really makes it hand to make changes to the backends. And to make custom applications that function in a different manor to the standard opensim setup. <BR><BR>I'm also unsure we really need a email field as part of the opensim db. I would think that should be part of the website account data. Which I believe most likely should be separate from opensim data. <BR><BR>The more data we have mixed together in the db's. The hander/ more work it becomes to maintain a opensim installation; to update it when changes are made to the database structures.<BR><BR><BR>For 0.6, lets think about some new layouts, to make things easier to customize and maintain?<BR><BR><BR><B><I>Stefan Andersson <stefan@tribalmedia.se></I></B> wrote:</P>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt">It is my firm belief, based on numerous integrations with custom backends, that we should separate the 'user' concept from the 'avatar' concept. On all Tribal Medias productions, the user logs on with a user id, not avatar first/last. In the real world (aka non-sl-grid 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 instances, agentId == userId == avatarId.<BR> <BR>What I mean is that an asset was uploaded and accessed by an 'agent', not a 'user' or an 'avatar'. This should be reflected in the tables as well.<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></P>
<DIV class=EC_MsoNormal style="TEXT-ALIGN: center" align=center>
<HR id=EC_EC_stopSpelling align=center width="100%" SIZE=2>
</DIV>
<P class=EC_MsoNormal style="MARGIN-BOTTOM: 12pt"><BR>To: opensim-dev@lists.berlios.de<BR>From: alan_webb@us.ibm.com<BR>Date: Mon, 3 Nov 2008 17:03:43 -0500<BR>Subject: Re: [Opensim-dev] Proposed additional db fields<BR><BR><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">As you say, e-mail in user information should be non-controversial, but it does highlight the difference between users and avatars. Does the OpenSim database actually reflect users? Or avatars? I thought the latter. What purpose will the e-mail address serve? I think there maybe more reluctance to provide this information than you might think. I'm prsonally nearly as opressed by providing my e-mail as I am my telephone number.</SPAN> <BR><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">Create time, given its one-to-one correspondence with an asset seems OK to me, but I think there is probably room for lots of discussion on ways to determine currency.</SPAN> <BR><BR><BR><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'"><BR>Best regards<BR>Alan<BR>-------------------<BR>T.J. Watson Research Center, Hawthorne, NY<BR>1-914-784-7286<BR>alan_webb@us.ibm.com</SPAN> <BR><BR><BR></P>
<TABLE class=EC_MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%" border=0>
<TBODY>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 40%; PADDING-TOP: 0.75pt" vAlign=top width="40%">
<P class=EC_MsoNormal><B><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Sean Dague <sdague@gmail.com></SPAN></B><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'"> </SPAN><BR><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Sent by: opensim-dev-bounces@lists.berlios.de</SPAN> <SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">11/03/2008 03:12 PM</SPAN> </P>
<TABLE class=EC_MsoNormalTable cellPadding=0 border=1>
<TBODY>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; BACKGROUND: white; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal style="TEXT-ALIGN: center" align=center><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Please respond to<BR>opensim-dev@lists.berlios.de</SPAN></P></TD></TR></TBODY></TABLE></TD>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; WIDTH: 59%; PADDING-TOP: 0.75pt" vAlign=top width="59%">
<TABLE class=EC_MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%" border=0>
<TBODY>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal style="TEXT-ALIGN: right" align=right><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">To</SPAN></P></TD>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">opensim-dev@lists.berlios.de</SPAN> </P></TD></TR>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal style="TEXT-ALIGN: right" align=right><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">cc</SPAN></P></TD>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top></TD></TR>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal style="TEXT-ALIGN: right" align=right><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">Subject</SPAN></P></TD>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 7.5pt; FONT-FAMILY: 'Arial','sans-serif'">[Opensim-dev] Proposed additional db fields</SPAN></P></TD></TR></TBODY></TABLE>
<P class=EC_MsoNormal> </P>
<TABLE class=EC_MsoNormalTable cellPadding=0 border=0>
<TBODY>
<TR>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top></TD>
<TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top></TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE>
<P class=EC_MsoNormal><BR><BR><BR><TT><SPAN style="FONT-SIZE: 10pt">I've got a couple of proposed db fields that I think we should add in,</SPAN></TT><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Courier New'"><BR><TT>but I want feedback before just putting it in.</TT><BR><BR><TT>users:</TT><BR><TT>* email - this is added by a lot of the web based management stacks,</TT><BR><TT>and would be really handy to be in the base user definition. I suspect</TT><BR><TT>this is non controversial.</TT><BR><BR><TT>assets:</TT><BR><TT>* create_time - the unix timestamp when the asset is created</TT><BR><TT>* access_time - the unix timestamp for last asset access</TT><BR><BR><TT>The rationale for these asset additional fields was some brainstorming</TT><BR><TT>this weekend on how we'd ever support asset reaping. Why not perfect,</TT><BR><TT>this may help in determining what are active assets, and what are</TT><BR><TT>ancient assets that may be suitable for reaping. Without these bits of</TT><BR><TT>information, we've got a hard time here.</TT><BR><BR><TT>Comments welcomed,</TT><BR><BR><TT> -Sean</TT><BR><BR><TT>-- </TT><BR><TT>Sean Dague / Neas Bade</TT><BR><TT>sdague@gmail.com</TT><BR><TT>http://dague.net</TT><BR><BR><BR><TT>_______________________________________________</TT><BR><TT>Opensim-dev mailing list</TT><BR><TT>Opensim-dev@lists.berlios.de</TT><BR><TT>https://lists.berlios.de/mailman/listinfo/opensim-dev</TT><BR></SPAN><BR>_______________________________________________<BR>Opensim-dev mailing list<BR>Opensim-dev@lists.berlios.de<BR>https://lists.berlios.de/mailman/listinfo/opensim-dev</P>
<P class=EC_MsoNormal> </P>
<BR></DIV></DIV></body>
</html>