Avatar portability version 2
From OpenSimulator
(Difference between revisions)
(→Basic Idea) |
(→Avatar Portability) |
||
| Line 13: | Line 13: | ||
only implemented 2nd, and would like to explan my idea: | only implemented 2nd, and would like to explan my idea: | ||
| − | + | == Avatar Portability == | |
In "users" table, "UserInventoryURL" and "UserAssetURL" have been there for a long time, and they are not used yet. My idea starts from the 2 properties; | In "users" table, "UserInventoryURL" and "UserAssetURL" have been there for a long time, and they are not used yet. My idea starts from the 2 properties; | ||
| − | + | === 1 UserInventoryUrl UserAssetUrl === | |
[[Image:avatar_portability_1.PNG]] | [[Image:avatar_portability_1.PNG]] | ||
*U1 is an user of GridService G1, so probably, U1's "UserInventoryURL" and "UserAssetURL" are pointing to G1's default Inventory/Asset server. | *U1 is an user of GridService G1, so probably, U1's "UserInventoryURL" and "UserAssetURL" are pointing to G1's default Inventory/Asset server. | ||
| Line 23: | Line 23: | ||
---- | ---- | ||
| − | + | === 2 Fetch data from multiple Inventory/Asset Data === | |
[[Image:avatar_portability_2.PNG]] | [[Image:avatar_portability_2.PNG]] | ||
*U1 login to R2, If U1 want to also bring in its apearance, R2 should have the ability that can '''get U1's appearance from U1's "UserInventoryUrl" and get U1's assets(textures) from "UserAssetUrl"'''. | *U1 login to R2, If U1 want to also bring in its apearance, R2 should have the ability that can '''get U1's appearance from U1's "UserInventoryUrl" and get U1's assets(textures) from "UserAssetUrl"'''. | ||
| Line 30: | Line 30: | ||
---- | ---- | ||
| − | + | === 3 ForeginAssetHashTable === | |
[[Image:avatar_portability_3.PNG]] | [[Image:avatar_portability_3.PNG]] | ||
Revision as of 00:48, 22 July 2008
Contents |
Basic Idea
To enable user avatar travel from a grid service to another grid service, There are 3 problems to be considered:
- How to enable foreign user login - Authentication
- (If a foreign user can login)How to get a foreign user's belongings(including appearance, inventory)
- This is discussed in this page
- AvatarPortability - Security
To achieve the 1st, client side changes are needed. SO, so far, I have only implemented 2nd, and would like to explan my idea:
Avatar Portability
In "users" table, "UserInventoryURL" and "UserAssetURL" have been there for a long time, and they are not used yet. My idea starts from the 2 properties;
1 UserInventoryUrl UserAssetUrl
- U1 is an user of GridService G1, so probably, U1's "UserInventoryURL" and "UserAssetURL" are pointing to G1's default Inventory/Asset server.
- R2 is a regionserver in GridService G2, so R2 fetches assets from G2's Asset server by default.
2 Fetch data from multiple Inventory/Asset Data
- U1 login to R2, If U1 want to also bring in its apearance, R2 should have the ability that can get U1's appearance from U1's "UserInventoryUrl" and get U1's assets(textures) from "UserAssetUrl".
- So, in this case, because an asset request("RequestImagePacket") only sends asset UUID to R2, R2 has to determine which asset server provides the reuqested UUID.
3 ForeginAssetHashTable
>R1 has to determine which asset server provides the reuqested UUID
- At the right-bottom of this picture, "ForeginAssetHashTable" is used to solve this.
- When an user login,
- region gets its "inventoryurl", "asseturl" from its "profile"
- region gets its appearance(UUIDs) from its "inventoryurl", and add the UUIDs into "ForeginAssetHashTable"
- Then when client send a "RequestImage(UUID)", RegionServer can look up into "ForeginAssetHashTable" to get the proper "AssetUrl"
Implementation
Authentication
Avatar Portability
1 Implementation - ForeginAssetHashTable.Add
2 Implementation - ForeginAssetHashTable.Get
3 Implementation - ForeginAssetHashTable.Remove
