Difference between revisions of "PyOGP Client Library Development"
Jump to navigation
Jump to search
(New page: This is the Development page for the Pyogp Client Library.) |
|||
| Line 1: | Line 1: | ||
This is the Development page for the [[Pyogp]] [[Pyogp/Client_Lib | Client Library]]. | This is the Development page for the [[Pyogp]] [[Pyogp/Client_Lib | Client Library]]. | ||
= Components (and supporting environmental details)= | |||
<br><b>Components</b> | |||
#Basic web server parts - deployable snap-in network framework. | |||
#*Login server | |||
#*Agent Domain | |||
#*Region Domain | |||
#Agent | |||
#Capabilities - need some way to POST and GET to capabilities | |||
#UDP Connections - some of the main functionality for a client happens in communication (2-way) with the server. | |||
#*Message Handlers - other than having huge switch states or specific cases, we should create some message handlers that will handle the specific messages coming in. The current way this is handled in the viewer is by having the client have a non-ported web server running in the viewer which handles the messages by parsing URLs in a local manner. We might consider something similar (this is because message handling is doing the same sort of thing as a web server, so might as well use currently working code). | |||
#**To the sim - event queue (see chttp, [[SLGOGP_Draft_1#Event_Queues]]), using Capabilities | |||
#**From the sim - when communication is sent to the client from the sim | |||
<br> | |||
<b>Protocols</b><br> | |||
[[Pyogp/Client_Lib/Protocols_Explained | Protocols_Explained]] - here's a listing of the protocols that we may implement, and the implementation details about them as well. | |||
#[[Pyogp/Protocols#Login | Login]] - ability to login to a login url, which will connect us to a simulator or agent domain | |||
#*The beta grid has an agent domain login accessible at https://login1.aditi.lindenlab.com/cgi-bin/auth.cgi | |||
#*Parameters = firstname, lastname, password (or md5-password as '$1$' + md5-hash) | |||
#*Regionuri list (log into the agent domain running on aditi, show up on vaak!). Use the regionuri parameter in viewers built from http://svn.secondlife.com/trac/linden/browser/branches/agent-domain-2 | |||
#**Note: people working with the agentd suggest trying one of 12035, 13000, 13001, and 13002. They say at LEAST 2 will work. Also note that the names listed below are not necessarily correct. They change frequently, so you can't count on being sent to the right named region. You should be OK going to the right region based on port, however. :) | |||
#**#http://sim1.vaak.lindenlab.com:13000 Dore | |||
#**#http://sim1.vaak.lindenlab.com:13001 Card | |||
#**#http://sim1.vaak.lindenlab.com:13002 Grigiano | |||
#**#http://sim1.vaak.lindenlab.com:12035 Island for Misfit Toys | |||
#**#http://sim2.vaak.lindenlab.com:12035 Ahern | |||
#**#http://sim2.vaak.lindenlab.com:13000 Miramare | |||
#**#http://sim2.vaak.lindenlab.com:13001 Morris | |||
#Presence - ability to be present on a grid | |||
Revision as of 07:35, 11 July 2008
This is the Development page for the Pyogp Client Library.
Components (and supporting environmental details)
Components
- Basic web server parts - deployable snap-in network framework.
- Login server
- Agent Domain
- Region Domain
- Agent
- Capabilities - need some way to POST and GET to capabilities
- UDP Connections - some of the main functionality for a client happens in communication (2-way) with the server.
- Message Handlers - other than having huge switch states or specific cases, we should create some message handlers that will handle the specific messages coming in. The current way this is handled in the viewer is by having the client have a non-ported web server running in the viewer which handles the messages by parsing URLs in a local manner. We might consider something similar (this is because message handling is doing the same sort of thing as a web server, so might as well use currently working code).
- To the sim - event queue (see chttp, SLGOGP_Draft_1#Event_Queues), using Capabilities
- From the sim - when communication is sent to the client from the sim
- Message Handlers - other than having huge switch states or specific cases, we should create some message handlers that will handle the specific messages coming in. The current way this is handled in the viewer is by having the client have a non-ported web server running in the viewer which handles the messages by parsing URLs in a local manner. We might consider something similar (this is because message handling is doing the same sort of thing as a web server, so might as well use currently working code).
Protocols
Protocols_Explained - here's a listing of the protocols that we may implement, and the implementation details about them as well.
- Login - ability to login to a login url, which will connect us to a simulator or agent domain
- The beta grid has an agent domain login accessible at https://login1.aditi.lindenlab.com/cgi-bin/auth.cgi
- Parameters = firstname, lastname, password (or md5-password as '$1$' + md5-hash)
- Regionuri list (log into the agent domain running on aditi, show up on vaak!). Use the regionuri parameter in viewers built from http://svn.secondlife.com/trac/linden/browser/branches/agent-domain-2
- Note: people working with the agentd suggest trying one of 12035, 13000, 13001, and 13002. They say at LEAST 2 will work. Also note that the names listed below are not necessarily correct. They change frequently, so you can't count on being sent to the right named region. You should be OK going to the right region based on port, however. :)
- http://sim1.vaak.lindenlab.com:13000 Dore
- http://sim1.vaak.lindenlab.com:13001 Card
- http://sim1.vaak.lindenlab.com:13002 Grigiano
- http://sim1.vaak.lindenlab.com:12035 Island for Misfit Toys
- http://sim2.vaak.lindenlab.com:12035 Ahern
- http://sim2.vaak.lindenlab.com:13000 Miramare
- http://sim2.vaak.lindenlab.com:13001 Morris
- Note: people working with the agentd suggest trying one of 12035, 13000, 13001, and 13002. They say at LEAST 2 will work. Also note that the names listed below are not necessarily correct. They change frequently, so you can't count on being sent to the right named region. You should be OK going to the right region based on port, however. :)
- Presence - ability to be present on a grid