<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmailquote
{mso-style-name:gmail_quote;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page Section1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-AU link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>It does impose an additional database lookup when fetching
assets, but it could lead to more efficient caching too. The latter I am
particularly interested in.<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Regards,<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Adam<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p> </o:p></span></p>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'>
<p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:
"Tahoma","sans-serif"'>From:</span></b><span lang=EN-US style='font-size:10.0pt;
font-family:"Tahoma","sans-serif"'> opensim-dev-bounces@lists.berlios.de
[mailto:opensim-dev-bounces@lists.berlios.de] <b>On Behalf Of </b>Teravus
Ovares<br>
<b>Sent:</b> Monday, 23 June 2008 1:21 PM<br>
<b>To:</b> opensim-dev@lists.berlios.de<br>
<b>Subject:</b> Re: [Opensim-dev] Proposal to eliminate the name,description
and invType fields from the assets db table<o:p></o:p></span></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<div>
<p class=MsoNormal>The only way for this to be extensable, and backwards
compatible enough really is to have the following structure.<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>InventoryItem ---->AssetUUID-----> DataHash<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>InventoryItem would be mapped to AssetUUID. AssetUUID
would have a many to one relationship with DataHash.. this would
allow for multiple UUIDs generated the random way to be associated with a
single data object in the database. <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal> <o:p></o:p></p>
</div>
<div>
<p class=MsoNormal>Best Regards<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><br>
Teravus<br>
<br>
<o:p></o:p></p>
</div>
<div>
<p class=MsoNormal><span class=gmailquote>On 6/23/08, <b>Sean Dague</b> <<a
href="mailto:sean@dague.net">sean@dague.net</a>> wrote:</span> <o:p></o:p></p>
<p class=MsoNormal style='margin-bottom:12.0pt'>On Mon, Jun 23, 2008 at
03:59:39PM -0400, Teravus Ovares wrote:<br>
> I'm not convinced the SHA1 UUID will be extensible enough to allow for<br>
> future plans. The idea is to not assume anything with a
UUID. Adding<br>
> assumptions increases scalability at the cost of extensibility.<br>
<br>
If we make UUID generation a static function that takes a reference to<br>
the content we should be able to implement all 5 RFC UUID types today<br>
(<a href="http://www.faqs.org/rfcs/rfc4122.html">http://www.faqs.org/rfcs/rfc4122.html</a>)<br>
<br>
Presumably we'd just do implementations for version 4 (random) and<br>
version 5 (sha1). UUID type will be detectable as there are reserved<br>
bits (though we'll probably need a path for "damn lindens don't follow<br>
UUID specs, so here are some hardcoded UUIDs that are in the system that<br>
don't follow specs").<br>
<br>
-Sean<br>
<br>
--<br>
__________________________________________________________________<br>
<br>
Sean
Dague
Mid-Hudson Valley<br>
sean at dague dot
net Linux
Users Group<br>
<a href="http://dague.net">http://dague.net</a>
<a href="http://mhvlug.org">http://mhvlug.org</a><br>
<br>
There is no silver bullet. Plus, werewolves make better neighbors<br>
than zombies, and they tend to keep the vampire population down.<br>
__________________________________________________________________<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.6 (GNU/Linux)<br>
<br>
iD8DBQFIYAN1SamXem9TdyYRAtTbAJ9Yzuf1Luhy2DltPmZnF2/CsyNmVACfef6D<br>
7lThzPS4+spuusW4kBrlYNk=<br>
=dyDj<br>
-----END PGP SIGNATURE-----<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
<o:p></o:p></p>
</div>
<p class=MsoNormal><o:p> </o:p></p>
</div>
</body>
</html>