Difference between revisions of "User:Saijanai Kuhn/Rez Avatar Capability"

From Second Life Wiki
Jump to navigation Jump to search
(attempt to make resource table for rez_avatar region host communication)
 
(12 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This will eventually be added to the [[SLGOGP_Draft_1 |Open Grid Protocol]]. it is taken from the [[Second_Life_Login_API_Strawman]].
=== rez_avatar Capability ===
=== rez_avatar Capability ===
This is the hypothetical proposed protocol for the future with many region domains.
This is the hypothetical proposed protocol for the future with many region domains.
Line 7: Line 9:
->
->
{'session_id': <s_id>, 'secure_session_id': <ssid>, 'circuit_code': <cc>, 'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <udp_port>, 'look_at': [lx, ly, lz]}
{'session_id': <s_id>, 'secure_session_id': <ssid>, 'circuit_code': <cc>, 'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <udp_port>, 'look_at': [lx, ly, lz]}


=====rez_avatar Capability (Resource Class)=====
=====rez_avatar Capability (Resource Class)=====
Line 15: Line 18:
|-
|-
|colspan="2"|
|colspan="2"|
''viewer <--> agent host''
''viewer --> agent host''
|-
|-
|Name
|Name
Line 21: Line 24:
|-
|-
|URL
|URL
|capability
|capabillity on agent host
|-
|-
|Verb
|Verb
Line 51: Line 54:
|-
|-
|colspan="2"|
|colspan="2"|
''agent host <--> region host''
''agent host --> region host''
|-
|-
|Name
|Name
| unknown
| rez_avatar Region Capability (working name)
|-
|-
|URL
|URL
| unknown
| internally known server to server communications URL
|-
|-
|Verb
|Verb
| unknown
| POST
|-
|-
|Request
|Request
|{'avatar_id': <a_id>, ..., 'position': [x, y, z]}
|{'avatar_id': <a_id>, 'position': [x, y, z], 'session_id':<uuid>, 'secure_session_id':<uuid>, 'circuit_code': <random>}
|-
|-
|
|
Line 69: Line 72:
|-
|-
|Response
|Response
|{'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <upd port>, 'circuit_code': <cc>, 'session_id': <s_id>, 'secure_session_id': <ssid>, 'look_at': [lx, ly, lz]} or 403 Forbidden
|{'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <upd port>, 'circuit_code': <cc>, 'session_id': <s_id>, 'secure_session_id': <ssid>, 'look_at': [lx, ly, lz]}
|-
|
|See above for explanation
|-
|or
|403 Forbidden
|-
|
|Access not allowed
|}
|}

Latest revision as of 18:09, 30 July 2008

This will eventually be added to the Open Grid Protocol. it is taken from the Second_Life_Login_API_Strawman.

rez_avatar Capability

This is the hypothetical proposed protocol for the future with many region domains.

rez_avatar agent host service'

stub

{'region_url': <r_url>, 'position': [x, y, z]} -> {'session_id': <s_id>, 'secure_session_id': <ssid>, 'circuit_code': <cc>, 'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <udp_port>, 'look_at': [lx, ly, lz]}


rez_avatar Capability (Resource Class)

rez_avatar Capability

viewer --> agent host

Name rez_avatar
URL capabillity on agent host
Verb POST
Request {'region_url': <r_url>, 'position': [x, y, z]}
RezAvatar agent host service
Response {'session_id': <s_id>, 'secure_session_id': <ssid>, 'circuit_code': <cc>, 'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <udp_port>, 'look_at': [lx, ly, lz]}

rez_avatar region host service

The rez_avatar agent host service invokes the rez_avatar region host service on behalf of the client.

{'avatar_id': <a_id>, ..., 'position': [x, y, z]}

->

{'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <upd port>, 'circuit_code': <cc>, 'session_id': <s_id>, 'secure_session_id': <ssid>, 'look_at': [lx, ly, lz]} or 403 Forbidden

rez_avatar Region Capability (Resource Class)

rez_avatar Region Capability

agent host --> region host

Name rez_avatar Region Capability (working name)
URL internally known server to server communications URL
Verb POST
Request {'avatar_id': <a_id>, 'position': [x, y, z], 'session_id':<uuid>, 'secure_session_id':<uuid>, 'circuit_code': <random>}
RezAvatar agent host service
Response {'seed_cap': <s_cap>, 'ip_address': <ip_address>, 'udp_port': <upd port>, 'circuit_code': <cc>, 'session_id': <s_id>, 'secure_session_id': <ssid>, 'look_at': [lx, ly, lz]}
See above for explanation
or 403 Forbidden
Access not allowed