<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Any chance we could make all textures available through REST? <br>
(LL is doing this, here's one example: <span class="attribute-value"><a class="moz-txt-link-freetext" href="http://secondlife.com/app/image/2fe686e5-6d14-d6ab-e080-6c13911c9c45/1">http://secondlife.com/app/image/2fe686e5-6d14-d6ab-e080-6c13911c9c45/1</a></span>)<br>
<br>
Stefan Andersson wrote:
<blockquote cite="midBLU134-W22745EDE3B3BF8EA141378D5C70@phx.gbl"
type="cite">
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>Recently, we've given distributed assets some thought. <br>
<br>
The base problem is that assets are (by sl legacy) requested by guid
from the viewer to the region, and the question is how the region would
know where to fetch that asset. So, in the case of avatar clothing, for
example, we send a 'shirt' asset that within itself contains a shirt
texture asset guid that is then requested from the viewer.<br>
<br>
Now, the region only forwarded the shirt asset from the assetserver, so
it actually doesn't know about the texture guid that was referenced
within it.<br>
<br>
But it still needs to know where to fetch the texture asset with
that guid.<br>
<br>
One solution that I can see would be if we scanned assets passing
thru the server and kept track of the guids within it, tagging them
with what asset they were referenced by. That would take a lot of
processing power.<br>
<br>
More thought needed.<br>
<br>
Best regards,<br>
Stefan Andersson<br>
Tribal Media AB<br>
<br>
<br>
<br>
<br>
<hr id="stopSpelling">
<br>
> From: <a class="moz-txt-link-abbreviated" href="mailto:chris.down@alcor.co.uk">chris.down@alcor.co.uk</a><br>
> To: <a class="moz-txt-link-abbreviated" href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
> Date: Wed, 21 May 2008 11:03:23 +0100<br>
> Subject: Re: [Opensim-dev] More on asset portability<br>
> <br>
> > If we clarified the roles of the user and inventory servers,
and kept<br>
> > all asset information in the inventory server, then it would
be much<br>
> > easier to use external inventory/asset servers. This means
that we want<br>
> > to move the AvatarAppearance API from the User server to the<br>
> > InventoryServer. The logic would be changed so that the
default<br>
> > inventory and asset servers are used unless the asseturl and<br>
> > inventoryurl are defined. That is, the grid would continue to
use its<br>
> > own asset and inventory servers unless you supply more
information.<br>
> > <br>
> > We plan to do work in this area soon, and welcome any
feedback and<br>
> > comment you have.<br>
> <br>
> This sounds like an good idea.<br>
> <br>
> Could this be extended such that the inventory table contained the
url of<br>
> the asset server that stores item? This would then lead to a
distributed<br>
> asset system. Not all assets would need to come from the same
asset server.<br>
> <br>
> Chris<br>
> <br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Opensim-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a>
<a class="moz-txt-link-freetext" href="https://lists.berlios.de/mailman/listinfo/opensim-dev">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>