[Opensim-dev] More on asset portability

[Justin Clark-Casey]

Dr Scofield wrote:
> Diva Canto wrote:
>> Any chance we could make all textures available through REST?
>> (LL is doing this, here's one example: 
>> http://secondlife.com/app/image/2fe686e5-6d14-d6ab-e080-6c13911c9c45/1)
> how about all assets in general?

In principle, isn't this possible today by exposing our REST asset 
server port?

Although I don't think osgrid's asset server could handle the extra load.

> 
>     cheers,
>     dr scofield
>> Stefan Andersson wrote:
>>> Recently, we've given distributed assets some thought.
>>>  
>>> 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.
>>>  
>>> 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.
>>>  
>>> But it still needs to know where to fetch the texture asset with 
>>> that guid.
>>>
>>> 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.
>>>  
>>> More thought needed.
>>>
>>> Best regards,
>>> Stefan Andersson
>>> Tribal Media AB
>>>  
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>>> From: chris.down at alcor.co.uk
>>>> To: opensim-dev at lists.berlios.de
>>>> Date: Wed, 21 May 2008 11:03:23 +0100
>>>> Subject: Re: [Opensim-dev] More on asset portability
>>>>
>>>>> If we clarified the roles of the user and inventory servers, and kept
>>>>> all asset information in the inventory server, then it would be much
>>>>> easier to use external inventory/asset servers. This means that 
>>> we want
>>>>> to move the AvatarAppearance API from the User server to the
>>>>> InventoryServer. The logic would be changed so that the default
>>>>> inventory and asset servers are used unless the asseturl and
>>>>> inventoryurl are defined. That is, the grid would continue to use its
>>>>> own asset and inventory servers unless you supply more information.
>>>>>
>>>>> We plan to do work in this area soon, and welcome any feedback and
>>>>> comment you have.
>>>> This sounds like an good idea.
>>>>
>>>> Could this be extended such that the inventory table contained the 
>>> url of
>>>> the asset server that stores item? This would then lead to a 
>>> distributed
>>>> asset system. Not all assets would need to come from the same asset 
>>> server.
>>>> Chris
>>>>
>>>> _______________________________________________
>>>> Opensim-dev mailing list
>>>> Opensim-dev at lists.berlios.de
>>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Opensim-dev mailing list
>>> Opensim-dev at lists.berlios.de
>>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>>   
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>   
> 
> 


-- 
justincc
Justin Clark-Casey
http://justincc.wordpress.com