Avatar portability version 2 - Revision history

MakoBot: Robot: Cosmetic changes

2012-03-04T04:43:44Z

Robot: Cosmetic changes

MakoBot: Robot: Cosmetic changes

2012-03-04T02:01:49Z

Robot: Cosmetic changes

MakoBot: Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2011-06-10T13:51:26Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

Makopoppo: it is proposal page

2011-04-16T02:43:12Z

it is proposal page

Ideia Boa at 10:44, 21 May 2009

2009-05-21T10:44:03Z

Lulurun: /* Implementation */

2008-07-22T15:40:41Z

‎Implementation

Lulurun: /* Agenda */

2008-07-22T15:22:39Z

‎Agenda

Lulurun: /* Implementation */

2008-07-22T15:17:18Z

‎Implementation

Lulurun: /* Implementation */

2008-07-22T15:15:47Z

‎Implementation

Lulurun: /* Agenda */

2008-07-22T15:15:39Z

‎Agenda

@@ Line 29: / Line 29: @@
 ** R2 fetches assets from Assetserver As2 by default.
 ** R2 gets inventory information from InventoryServer I2 by default.
-[[Image:avatar_portability_v2_1.PNG]]
+[[File:avatar_portability_v2_1.PNG]]
 === avatar portability ===
@@ Line 41: / Line 41: @@
 UGAI server, but also external Inventory, Asset, Avatar service.
-[[Image:avatar_portability_v2_2.PNG]]
+[[File:avatar_portability_v2_2.PNG]]
 '''Then "AvatarPortability" can be subdivided into 2 goals:'''
@@ Line 94: / Line 94: @@
 * Client extract the UUIDs, and sends a "RequestImagePacket" to request the actual asset data.
 * RegionServer receives the AssetUUID and passes it to AssetServer to get the asset.
-[[Image:avatar_portability_v2_3-1.PNG]]
+[[File:avatar_portability_v2_3-1.PNG]]
 * Considering only 1 GridService, there is no problem, but if RegionServer knows more than 1 asset server, RegionServer has to determine which assetserver should be used.
 * Here '''ForeignAssetHashTable''' is used to solve this problem. (The detailed implementation is shown in following section.)
@@ Line 101: / Line 101: @@
 *# R2 looks up into "ForeignAssetHashTable" to find the AssetServerUrl,(if not found, returns the default url)
 *# R2 use the returned AssetServerUrl to get asset data.
-[[Image:avatar_portability_v2_3.PNG]]
+[[File:avatar_portability_v2_3.PNG]]
 == Implementation ==
@@ Line 112: / Line 112: @@
 === 1 Implementation - ForeginAssetHashTable.Add ===
-[[Image:avatar_portability_4-1.PNG]]
+[[File:avatar_portability_4-1.PNG]]
 === 2 Implementation - ForeginAssetHashTable.Get ===
-[[Image:avatar_portability_4-2.PNG]]
+[[File:avatar_portability_4-2.PNG]]
 === 3 Implementation - ForeginAssetHashTable.Remove ===
-[[Image:avatar_portability_4-3.PNG]]
+[[File:avatar_portability_4-3.PNG]]

@@ Line 21: / Line 21: @@
 === definition ===
-*User U1 resgitered at GridService G1
+* User U1 resgitered at GridService G1
 ** U1's inventory information is stored in InventoryServer I1
 ** U1's assets are stored in AssetServer As1
 ** U1's appearance information is served by AvatarService Av1
-*RegionServer R2 serves a sim at GridService G2
+* RegionServer R2 serves a sim at GridService G2
 ** R2 fetches assets from Assetserver As2 by default.
 ** R2 gets inventory information from InventoryServer I2 by default.
@@ Line 34: / Line 34: @@
 AvatarPortability (or called "grid interoperability") is
-*U1 login to R2
+* U1 login to R2
-**U1's appearance at G1 can be seen from any other client which is connecting to R2.
+** U1's appearance at G1 can be seen from any other client which is connecting to R2.
-**U1 can CRUD(Create/Read/Update/Delete) its inventory/appearance through R2.
+** U1 can CRUD(Create/Read/Update/Delete) its inventory/appearance through R2.
 This means, (in the fig. 2) R2 should have the ability to connect not only its default
@@ Line 50: / Line 50: @@
 more information can be found at:
-*http://en.wikipedia.org/wiki/Yadis
+* http://en.wikipedia.org/wiki/Yadis
-*http://en.wikipedia.org/wiki/XRDS
+* http://en.wikipedia.org/wiki/XRDS
 A sample XRDS for U1 can be like:
@@ Line 80: / Line 80: @@
    </xrds:XRDS>
-*There are more than one way can be considered to pass U1's XRDS file to R2
+* There are more than one way can be considered to pass U1's XRDS file to R2
-**[[OpenID for data portability in virtual world]]
+** [[OpenID for data portability in virtual world]]
 REASONS for proposing XRDS
@@ Line 91: / Line 91: @@
 Why it is a problem ? The asset download process is described below:
-*RegionServer sends user/prims' Texture UUID to the client.
+* RegionServer sends user/prims' Texture UUID to the client.
-*Client extract the UUIDs, and sends a "RequestImagePacket" to request the actual asset data.
+* Client extract the UUIDs, and sends a "RequestImagePacket" to request the actual asset data.
-*RegionServer receives the AssetUUID and passes it to AssetServer to get the asset.
+* RegionServer receives the AssetUUID and passes it to AssetServer to get the asset.
 [[Image:avatar_portability_v2_3-1.PNG]]
-*Considering only 1 GridService, there is no problem, but if RegionServer knows more than 1 asset server, RegionServer has to determine which assetserver should be used.
+* Considering only 1 GridService, there is no problem, but if RegionServer knows more than 1 asset server, RegionServer has to determine which assetserver should be used.
-*Here '''ForeignAssetHashTable''' is used to solve this problem. (The detailed implementation is shown in following section.)
+* Here '''ForeignAssetHashTable''' is used to solve this problem. (The detailed implementation is shown in following section.)
-*#when U1 login to R2, R2 register U1's owned asset UUIDs to "ForeignAssetHashTable".
+*# when U1 login to R2, R2 register U1's owned asset UUIDs to "ForeignAssetHashTable".
-*#Client sends a RequestImagePacket
+*# Client sends a RequestImagePacket
-*#R2 looks up into "ForeignAssetHashTable" to find the AssetServerUrl,(if not found, returns the default url)
+*# R2 looks up into "ForeignAssetHashTable" to find the AssetServerUrl,(if not found, returns the default url)
-*#R2 use the returned AssetServerUrl to get asset data.
+*# R2 use the returned AssetServerUrl to get asset data.
 [[Image:avatar_portability_v2_3.PNG]]
 == Implementation ==
-*All the implementation described here are already finished
+* All the implementation described here are already finished
-**The testing environment will be made public after solving the "[[security vulnerability brought by non-check inventory service|security]]" issues.
+** The testing environment will be made public after solving the "[[security vulnerability brought by non-check inventory service|security]]" issues.
-*Just for appearance portability, asseturl and inventoryurl are enough, so temporarily just use the 2 existing properties.
+* Just for appearance portability, asseturl and inventoryurl are enough, so temporarily just use the 2 existing properties.
-*XRDS is not implemented
+* XRDS is not implemented
 === 1 Implementation - ForeginAssetHashTable.Add ===

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Template:Quicklinks}}
+{{Quicklinks}}
 {{proposal}}

@@ Line 1: / Line 1: @@
 __NOTOC__
 {{Template:Quicklinks}}
 [[User:Lulurun]]

← Older revision		Revision as of 10:44, 21 May 2009
Line 1:		Line 1:
		+	__NOTOC__
		+	{{Template:Quicklinks}}
		+
	[[User:Lulurun]]		[[User:Lulurun]]

@@ Line 11: / Line 11: @@
 To achieve the 1st, client side changes are needed. SO, so far, I have
-only implemented 2nd, and would like to explan my idea:
+only implemented the 2nd and the 3rd, and would like to explan my idea:
 == Basic Idea ==

@@ Line 8: / Line 8: @@
 # '''(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]]
+# [[security vulnerability brought by non-check inventory service|Security]]
 To achieve the 1st, client side changes are needed. SO, so far, I have