Difference between revisions of "Protocol Documentation"
Eddy Stryker (talk | contribs) (The big protocol documentation skeleton, all on one page as requested) |
Eddy Stryker (talk | contribs) (Adding some links to existing descriptions) |
||
| Line 4: | Line 4: | ||
=Message Formats= | =Message Formats= | ||
==Binary UDP== | ==Binary UDP== | ||
The packets in the binary UDP protocol are defined by a message template file, the format is described in [[Message Layout]]. The layout details for constructing packets based on the message layout is detailed in [[Packet Layout]]. | |||
==LLSD== | ==LLSD== | ||
The Linden Lab Structured Data system is an abstract way of representing data with some strong types. Three serialization formats are supported including binary, XML, and notation which are described in [[LLSD]]. | |||
==XML-RPC== | ==XML-RPC== | ||
The initial exchange with the login server uses XML-RPC. | |||
== | |||
==Capabilities== | |||
The [[Capabilities]] system allows viewers to request abilities and be temporarily granted those abilities through a unique URL. The transport format is LLSD XML, and clients can either post new events to CAPS URLs or wait for events to come from the server on the event queue connection the client holds open. | |||
=Protocol Systems= | =Protocol Systems= | ||
Revision as of 12:44, 28 September 2007
Protocol Documentation
Message Formats
Binary UDP
The packets in the binary UDP protocol are defined by a message template file, the format is described in Message Layout. The layout details for constructing packets based on the message layout is detailed in Packet Layout.
LLSD
The Linden Lab Structured Data system is an abstract way of representing data with some strong types. Three serialization formats are supported including binary, XML, and notation which are described in LLSD.
XML-RPC
The initial exchange with the login server uses XML-RPC.
Capabilities
The Capabilities system allows viewers to request abilities and be temporarily granted those abilities through a unique URL. The transport format is LLSD XML, and clients can either post new events to CAPS URLs or wait for events to come from the server on the event queue connection the client holds open.