Difference between revisions of "XMPPComponentProtocol"

Jump to navigation Jump to search
2 bytes removed ,  02:22, 17 December 2020
m
no edit summary
m
 
m
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== XMPP Component Protocol ==
== 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 [http://xmpp.org/extensions/xep-0114.html Jabber Component Protocol specification (XEP-0114)]. This page documents arguments for and requirements of a superseding protocol.
The XMPP network has long included a wire protocol that enables trusted components to connect to XMPP servers. This has since been documented in the [https://xmpp.org/extensions/xep-0114.html Jabber Component Protocol specification (XEP-0114)]. This page documents arguments for and requirements of a superseding protocol.


=== Arguments  ===
=== Arguments  ===
Arguments for wanting a replacement component protocol:
Arguments for wanting a replacement component protocol:
* Have XMPP 1.0 XML Streams
* Have XMPP 1.0 XML Streams
* More intricate XEPs that require access to user information like roster and presence. An example is the [http://xmpp.org/extensions/xep-0163.html Personal Eventing Protocol (XEP-0163)].
* More intricate XEPs that require access to user information like roster and presence. An example is the [https://xmpp.org/extensions/xep-0163.html Personal Eventing Protocol (XEP-0163)].
* Handle several JIDs through one connection
* Handle several JIDs through one connection


216

edits

Navigation menu