Difference between revisions of "Current Sim Capabilities"
(deleted category sim capabilities as it didn't fit with the flow of the article) |
|||
| Line 28: | Line 28: | ||
:• [[ChatSessionRequest_CAP|ChatSessionRequest]] | |||
:• [[CopyInventoryFromNotecard_CAP|CopyInventoryFromNotecard]] | |||
:• [[DispatchRegionInfo_CAP|DispatchRegionInfo]] | |||
:• [[EventQueueGet_CAP|EventQueueGet]] | |||
:• [[MapLayer_CAP|MapLayer]] | |||
:• [[MapLayerGod_CAP|MapLayerGod]] | |||
:• [[NewFileAgentInventory_CAP|NewFileAgentInventory]] | |||
:• [[ParcelGodReserveForNewbie_CAP|ParcelGodReserveForNewbie]] | |||
:• [[ParcelVoiceInfoRequest_CAP|ParcelVoiceInfoRequest]] | |||
:• [[ProvisionVoiceAccountRequest_CAP|ProvisionVoiceAccountRequest]] | |||
:• [[RemoteParcelRequest_CAP|RemoteParcelRequest]] | |||
:• [[RequestTextureDownload_CAP|RequestTextureDownload]] | |||
:• [[SearchStatRequest_CAP|SearchStatRequest]] | |||
:• [[SearchStatTracking_CAP|SearchStatTracking]] | |||
:• [[SendPostcard_CAP|SendPostcard]] | |||
:• [[SendUserReport_CAP|SendUserReport]] | |||
:• [[SendUserReportWithScreenshot_CAP|SendUserReportWithScreenshot]] | |||
:• [[ServerReleaseNotes_CAP|ServerReleaseNotes]] | |||
:• [[UpdateGestureAgentInventory_CAP|UpdateGestureAgentInventory]] | |||
:• [[UpdateNotecardAgentInventory_CAP|UpdateNotecardAgentInventory]] | |||
:• [[UpdateScriptAgentInventory_CAP|UpdateScriptAgentInventory]] | |||
:• [[UpdateGestureTaskInventory_CAP|UpdateGestureTaskInventory]] | |||
:• [[UpdateNotecardTaskInventory_CAP|UpdateNotecardTaskInventory]] | |||
:• [[UpdateScriptTaskInventory_CAP|UpdateScriptTaskInventory]] | |||
:• [[ViewerStartAuction_CAP|ViewerStartAuction]] | |||
:• [[UntrustedSimulatorMessage_CAP|UntrustedSimulatorMessage]] | |||
:• [[ViewerStats_CAP|ViewerStats]] | |||
Revision as of 04:11, 21 November 2007
Introduction
In the current protocols, there appear to be at least 2 kinds of capabilities: Sim capabilities and Sub-Capabilities obtained from the Sim Capability. The current login protocols return a "seed-capability" which is actually the Sim-Capability of the sim the avatar enters upon performing a full login. This will change with the new login protocols.
Accessing Capabilities
A typical capability is of the form: https://sim1234.agni.lindenlab.com:12345/cap/UUID
In the current client, sim capabilities are accessed via an https request of the form:
https request {POST, URL:port, path, body, header}
where
- • URL:port is of the form: sim1234.agni.lindenlab.com:12345;
- • path is of the form: /cap/UUID;
- • body is an xml-encoded LLSD array of the form: <llsd><array><string>request1</string><string>request2</string></array></llsd>
- • Header is of the form: "content-type": "application/xml";
The response from a sim capability transaction is an xml-encoded LLSD dictionary with key, value pairs in the form:
- • <llsd><map><key>request1</key><string>Capability1</string><key>request2</key><string>Capability2</string</map></llsd>
sub-capabilities apparently use the same protocol, but the body of the https request is dependent on which capability is used, as is the result.
- • ChatSessionRequest
- • CopyInventoryFromNotecard
- • DispatchRegionInfo
- • EventQueueGet
- • MapLayer
- • MapLayerGod
- • NewFileAgentInventory
- • ParcelGodReserveForNewbie
- • ParcelVoiceInfoRequest
- • ProvisionVoiceAccountRequest
- • RemoteParcelRequest
- • RequestTextureDownload
- • SearchStatRequest
- • SearchStatTracking
- • SendPostcard
- • SendUserReport
- • SendUserReportWithScreenshot
- • ServerReleaseNotes
- • UpdateGestureAgentInventory
- • UpdateNotecardAgentInventory
- • UpdateScriptAgentInventory
- • UpdateGestureTaskInventory
- • UpdateNotecardTaskInventory
- • UpdateScriptTaskInventory
- • ViewerStartAuction
- • UntrustedSimulatorMessage
- • ViewerStats