https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&feed=atom&action=history
XMPPComponentProtocol - Revision history
2024-03-28T18:31:03Z
Revision history for this page on the wiki
MediaWiki 1.37.1
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=13342&oldid=prev
Neustradamus at 02:22, 17 December 2020
2020-12-17T02:22:57Z
<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:22, 17 December 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l5">Line 5:</td>
<td colspan="2" class="diff-lineno">Line 5:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Arguments for wanting a replacement component protocol:</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Arguments for wanting a replacement component protocol:</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Have XMPP 1.0 XML Streams</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Have XMPP 1.0 XML Streams</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* More intricate XEPs that require access to user information like roster and presence. An example is the [<del style="font-weight: bold; text-decoration: none;">http</del>://xmpp.org/extensions/xep-0163.html Personal Eventing Protocol (XEP-0163)].</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* More intricate XEPs that require access to user information like roster and presence. An example is the [<ins style="font-weight: bold; text-decoration: none;">https</ins>://xmpp.org/extensions/xep-0163.html Personal Eventing Protocol (XEP-0163)].</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Handle several JIDs through one connection</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Handle several JIDs through one connection</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
</table>
Neustradamus
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=13341&oldid=prev
Neustradamus at 02:22, 17 December 2020
2020-12-17T02:22:39Z
<p></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 02:22, 17 December 2020</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1">Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== XMPP Component Protocol ==</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>== XMPP Component Protocol ==</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>The <del style="font-weight: bold; text-decoration: none;">Jabber </del>network has long included a wire protocol that enables trusted components to connect to <del style="font-weight: bold; text-decoration: none;">Jabber </del>servers. This has since been documented in the [<del style="font-weight: bold; text-decoration: none;">http</del>://xmpp.org/extensions/xep-0114.html Jabber Component Protocol specification (XEP-0114)]. This page documents arguments for and requirements of a superseding protocol.</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>The <ins style="font-weight: bold; text-decoration: none;">XMPP </ins>network has long included a wire protocol that enables trusted components to connect to <ins style="font-weight: bold; text-decoration: none;">XMPP </ins>servers. This has since been documented in the [<ins style="font-weight: bold; text-decoration: none;">https</ins>://xmpp.org/extensions/xep-0114.html Jabber Component Protocol specification (XEP-0114)]. This page documents arguments for and requirements of a superseding protocol.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Arguments ===</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== Arguments ===</div></td></tr>
</table>
Neustradamus
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=8280&oldid=prev
Neustradamus at 16:29, 21 July 2010
2010-07-21T16:29:53Z
<p></p>
<p><b>New page</b></p><div>== XMPP Component Protocol ==<br />
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.<br />
<br />
=== Arguments ===<br />
Arguments for wanting a replacement component protocol:<br />
* Have XMPP 1.0 XML Streams<br />
* 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)].<br />
* Handle several JIDs through one connection<br />
<br />
=== Links ===<br />
[http://codex.xiaoka.com/wiki/_media/jabberd2:component.html Jabberd2's component protocol]<br />
<br />
=== Current discussions ===<br />
The most likely approach to improve the protocol is:<br />
* First define a simple API of target operations.<br />
* Propose an XMPP formalism for the API using "adhoc commands" that can be handled by the server.<br />
<br />
One of the first target in the API is roster item addition (with nickname and subscription) and deletion.<br />
<br />
=== Restrictions to remove ===<br />
We discussed the removal of the restriction in XEP-0114 that prevent a component to send packets on the behalf of a user of the server itself.</div>
Neustradamus
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=8278&oldid=prev
Mremond: /* Restriction to remove */
2007-02-26T14:28:54Z
<p><span dir="auto"><span class="autocomment">Restriction to remove</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 14:28, 26 February 2007</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l22">Line 22:</td>
<td colspan="2" class="diff-lineno">Line 22:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>One of the first target in the API is roster item addition (with nickname and subscription) and deletion.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>One of the first target in the API is roster item addition (with nickname and subscription) and deletion.</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>== <del style="font-weight: bold; text-decoration: none;">Restriction </del>to remove ==</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>== <ins style="font-weight: bold; text-decoration: none;">Restrictions </ins>to remove ==</div></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>We discussed the removal of the restriction in XEP-0114 that prevent a component to send packets on the behalf of a user of the server itself.</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>We discussed the removal of the restriction in XEP-0114 that prevent a component to send packets on the behalf of a user of the server itself.</div></td></tr>
</table>
Mremond
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=8277&oldid=prev
Mremond at 14:28, 26 February 2007
2007-02-26T14:28:36Z
<p></p>
<p><b>New page</b></p><div>= XMPP Component Protocol =<br />
<br />
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://www.jabber.org/jeps/jep-0114.html Jabber Component Protocol specification (JEP-0114)]. This page documents arguments for and requirements of a superseding protocol.<br />
<br />
== Arguments ==<br />
<br />
Arguments for wanting a replacement component protocol:<br />
<br />
* Have XMPP 1.0 XML Streams<br />
* 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)].<br />
* Handle several JIDs through one connection<br />
<br />
== Links ==<br />
[http://jabberd.jabberstudio.org/dev/docs/component.shtml Jabberd2's component protocol]<br />
<br />
== Current discussions ==<br />
<br />
The most likely approach to improve the protocol is:<br />
* First define a simple API of target operations.<br />
* Propose an XMPP formalism for the API using "adhoc commands" that cna be handled by the server.<br />
<br />
One of the first target in the API is roster item addition (with nickname and subscription) and deletion.<br />
<br />
== Restriction to remove ==<br />
<br />
We discussed the removal of the restriction in XEP-0114 that prevent a component to send packets on the behalf of a user of the server itself.</div>
Mremond
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=8274&oldid=prev
Ralphm: /* Arguments */
2006-07-18T19:58:22Z
<p><span dir="auto"><span class="autocomment">Arguments</span></span></p>
<table style="background-color: #fff; color: #202122;" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #202122; text-align: center;">Revision as of 19:58, 18 July 2006</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l8">Line 8:</td>
<td colspan="2" class="diff-lineno">Line 8:</td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><br/></td></tr>
<tr><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Have XMPP 1.0 XML Streams</div></td><td class="diff-marker"></td><td style="background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* Have XMPP 1.0 XML Streams</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* More intricate JEPs that require access to user information like roster and presence. An example is the</div></td><td class="diff-marker" data-marker="+"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>* 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)].</div></td></tr>
<tr><td class="diff-marker" data-marker="−"></td><td style="color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del style="font-weight: bold; text-decoration: none;"> </del>[http://www.jabber.org/jeps/jep-0163.html Personal Eventing Protocol (JEP-0163)].</div></td><td colspan="2" class="diff-side-added"></td></tr>
</table>
Ralphm
https://wiki.xmpp.org/web/index.php?title=XMPPComponentProtocol&diff=8273&oldid=prev
Ralphm: First take on developing a new component protocol
2006-07-18T19:58:04Z
<p>First take on developing a new component protocol</p>
<p><b>New page</b></p><div>= XMPP Component Protocol =<br />
<br />
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://www.jabber.org/jeps/jep-0114.html Jabber Component Protocol specification (JEP-0114)]. This page documents arguments for and requirements of a superseding protocol.<br />
<br />
== Arguments ==<br />
<br />
Arguments for wanting a replacement component protocol:<br />
<br />
* Have XMPP 1.0 XML Streams<br />
* More intricate JEPs that require access to user information like roster and presence. An example is the<br />
[http://www.jabber.org/jeps/jep-0163.html Personal Eventing Protocol (JEP-0163)].</div>
Ralphm