Difference between revisions of "XMPPComponentProtocol"
Jump to navigation
Jump to search
(First take on developing a new component protocol) |
|||
| Line 8: | Line 8: | ||
* Have XMPP 1.0 XML Streams | * Have XMPP 1.0 XML Streams | ||
* More intricate JEPs that require access to user information like roster and presence. An example is the | * More intricate JEPs that require access to user information like roster and presence. An example is the [http://www.jabber.org/jeps/jep-0163.html Personal Eventing Protocol (JEP-0163)]. | ||
Revision as of 19:58, 18 July 2006
XMPP Component Protocol
The Jabber network has long included a wire protocol that enables trusted components to connect to Jabber servers. This has since been documented in the Jabber Component Protocol specification (JEP-0114). This page documents arguments for and requirements of a superseding protocol.
Arguments
Arguments for wanting a replacement component protocol:
- Have XMPP 1.0 XML Streams
- More intricate JEPs that require access to user information like roster and presence. An example is the Personal Eventing Protocol (JEP-0163).