Difference between revisions of "Viewer URI Name Space"
Jump to navigation
Jump to search
James Linden (talk | contribs) (Removed app/help, as it is not supported in the current (1.20) code base.) |
James Linden (talk | contribs) |
||
Line 12: | Line 12: | ||
The new URL scheme has 3 slashes, and allows direct control of the user interface and login. For example, secondlife:///app/login | The new URL scheme has 3 slashes, and allows direct control of the user interface and login. For example, secondlife:///app/login | ||
Most secondlife:///app URLs only work from browser instances running inside Second Life because of a denial-of-service attack using secondlife:///app/teleport links to force repeated teleports. SLURLs that work with external browsers include: | |||
* secondlife://<region name> | |||
* secondlife:///app/login | |||
'''secondlife://''' | '''secondlife://''' | ||
Line 23: | Line 28: | ||
*** /<agent_id> | *** /<agent_id> | ||
**** /about ''open agent's profile, with 2nd Life tab selected'' | **** /about ''open agent's profile, with 2nd Life tab selected'' | ||
** /login | ** /login ''log in on launch. External and internal browsers.'' | ||
*** see below for query parameters, of course, values are URL escaped | *** see below for query parameters, of course, values are URL escaped | ||
** /event | ** /event |
Revision as of 13:50, 15 September 2008
aka Viewer URL Namespace
aka SLAPP URLs
aka Application SLURL
The SL client supports links of the format secondlife://Region/123/45/67/, which have traditionally specified a region name and x/y/z location. This means "open Second Life and show Region on the world map".
The new URL scheme has 3 slashes, and allows direct control of the user interface and login. For example, secondlife:///app/login
Most secondlife:///app URLs only work from browser instances running inside Second Life because of a denial-of-service attack using secondlife:///app/teleport links to force repeated teleports. SLURLs that work with external browsers include:
- secondlife://<region name>
- secondlife:///app/login
- <region_name> log in to this region or, if logged in, show information and offer teleport
- /<local_x> optional X position, defaults to 128
- /<local_y> optional Y position, defaults to 128
- /<local_z> optional Z position, defaults to 0
- /<local_y> optional Y position, defaults to 128
- /<local_x> optional X position, defaults to 128
- /app
- /agent
- /<agent_id>
- /about open agent's profile, with 2nd Life tab selected
- /<agent_id>
- /login log in on launch. External and internal browsers.
- see below for query parameters, of course, values are URL escaped
- /event
- /<event_id>
- /about open floater describing event
- /<event_id>
- /group
- /<group_id>
- /about open floater describing group
- /create open the create group dialog, added in 1.20
- /list
- /show open the list of groups to which user belongs, added in 1.20
- /<group_id>
- /parcel
- /<parcel_id>
- /about open floater describing place
- /<parcel_id>
- /classified
- /<classified_id>
- /about open floater describing classified
- /<classified_id>
- /region
- /<region_id>
- /about information from database about that region? list of parcels? covenant?
- /<region_id>
- /teleport
- /<region_name> teleport instantly to this region, no dialog
- /<local_x> optional X position, defaults to 128
- /<local_y> optional Y position, defaults to 128
- /<local_z> optional Z position, defaults to 0
- /<local_y> optional Y position, defaults to 128
- /<local_x> optional X position, defaults to 128
- /<region_name> teleport instantly to this region, no dialog
- /agent
This could be extended to things like:
- /app/event/<event_id>/subscribe to register for notifications
- /app/parcel/<parcel_id>/teleport to teleport to a specific location
- /app/agent/<agent_id>/im to start IM session
Login Query Parameters
first | the account first name |
last | the account last name |
session | the secure session id |
location | login location, format TBD, optional |