<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
It is my impression that adressing by uri/url has been a goal for the last 1.5 years or so.<BR>
<BR>
I'd be interested in hearing if there's actually anybody _not_ wanting us to work towards that.<BR>
<BR>
The only issue that I can see would be in regards to SL compatibility. I have started to poc an approach where guid-based adressing of resources is considered a thing purely between the viewer and the content endpoint (aka the region) - that the region acts as a 'proxy' translating guids to uris and back as needed. So far the code is merely stubs, so I haven't got to the point of proofing it, but I believe you all understand what I'm saying. Have a look at what uses the fairly new ContainsReferences method on AssetBase to see where I was going.<BR><BR>Best regards,<BR>Stefan Andersson<BR><BR><BR><BR> <BR>> Date: Fri, 1 May 2009 08:56:57 +0300<BR>> From: tommi.s.e.laukkanen@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: [Opensim-dev] Alternatively Identifying Assets using URL's<BR>> <BR>> If we do not consider SL restrictions for a second and look to the<BR>> future it would be nice to discuss the following which popped out from<BR>> dahlias idea of supporting loading textures from websites directly and<BR>> Stefans suggestion of using strings as ids in the standard format<BR>> thread:<BR>> <BR>> It is good to consider supporting identification of assets by<BR>> traditional urls. Some public asset servers could be www servers or<BR>> svn http servers. As all 3d modeling programs are refering to<BR>> aggregate assets using file paths, it would be easy to upload the<BR>> model to SVN http server and then using viewer pull out the model and<BR>> aggregate assets for viewing. This could be alternative asset<BR>> distribution model. it could work through region asset cache or<BR>> directly from viewer to the http server. This could be much more<BR>> scalable than the current model. I realize this is a threat to the<BR>> data consistency as models and aggregate assets are not saved to<BR>> relational database which could safeguard relations. It is also viable<BR>> only for completely public content but I assume considerable portion<BR>> of the vw content is likely to be freely distributable.<BR>> <BR>> This would be in practice support for "importing" content from web on the fly.<BR>> <BR>> -tommi<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>