[Opensim-dev] Proposal to subdivide the assets table

[Destiny Niles]

This is similar to how Linden Lab handle assets. Not only are the
table different but also the server is different. I tried to find the
information that I got from a Linden once on how assets are handle but
could not find it.
The in summary (specific details might be wrong): A central asset
server have everything you see in your inventory.
When an asset is used in-world a copy is transfered to the local
sim/region/island asset server (database) this includes attachments.
Non-copy items are flagged as being checked out.
The local sim keep tracks of assests within it.
If I ever find the information about how Linden Lab handles assets
I'll forward it


On Thu, Jun 26, 2008 at 3:55 PM, Destiny Niles <techiedavid at gmail.com> wrote:
> On Thu, Jun 26, 2008 at 9:27 AM, liu xiaolu <lulurun at gmail.com> wrote:
>> Hi everyone,
>>
>> my proposal is to subdivide current assets table into 2 tables:
>> user_assets  : for user owned assets (mainly in inventory, appearance,
>> attachment, ...)
>>   user_asset is used by UGAI servers
>> region_assets: for region owned assets, sounds, textures(including sun,
>> moon, ...)
>>   region_asset is used by region servers
>>
>> I wrote the whole, detailed idea at:
>> http://opensimulator.org/wiki/User:Lulurun#proposal_to_subdivide_the_assets_table
>> Please have a look at it, here is only a brief introduction.
>>
>> This could bring us many advantages such as:
>> 0. increase the dispersity of asset data, clarify the responsibility of each
>> server.
>> Currently, all of the asset data is stored in assets table, managed by
>> assetserver.
>> This would cause some problems:
>>  1. assets table keeps growing in a fast pace.
>>  2. hard to determine which asset is belongs to inactive regions (when you
>> want to "clean"
>> the assets table).
>>  3. assetserver not only serves users' data but also regions' data, if
>> something happened to
>> assetserver both of avatar and prims will become gray.
>> To separate assets table can not only solve these problems, but also brings
>> minor benefits
>> such like: reduce the responsibility of assetserver, disperse the asset
>> requests(especially
>> for big grid service), lower the risk of losing data, ...
>>
>> 1. for Data Portability in virtual world
>> For grid admin,
>>  * you can concentrate on managing only user(not region owner) relavent
>> information
>>    like "users, avatarappearance, inventory"
>>  * it can reduce the vulnerability caused by foreign assets.
>>  * when a region leaves your grid, you don't have to worry about its assets
>> becoming garbage.
>>   - on the other hand, this also good for region owners.
>> For when a user registers their region server with a grid,
>>  * When you want to switch your sim to a new grid, "prims, primshapes,
>> terrain, region_asset"
>>    are always tied-up together. the only thing you need to do is to edit
>> UGAI servers URI in
>>    your OpenSim.ini
>>
>> For more advantages, please have a look at
>> http://opensimulator.org/wiki/User:Lulurun#Advantages
>>
>> If this is a good way to go, not so many changes is needed:
>> * UGAI servers would remain as they used to be.
>> * VW user won't feel anything different.
>> * Of course this should be a option in OpenSim.ini so that we can
>> enable/disable/config
>> * Just need to add supports for a new table "RegionAssets" with the same
>> structure as "assets".
>> * AssetClient in RegionServer should be improved to be able to get assets
>> from mutilple servers.
>>
>> For more detailed plan of the implementation, please have a look at
>> http://opensimulator.org/wiki/User:Lulurun#Implementation
>>
>> Any advice, comment, thought is appreciate.
>>
>> --
>> Lulurun
>> regards
>>
>>
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>>
>