10
edits
Difference between revisions of "XMPPComponentProtocol"
Jump to navigation
Jump to search
XMPPComponentProtocol (view source)
Revision as of 14:28, 26 February 2007
, 14:28, 26 February 2007no edit summary
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
* 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 [http://www.jabber.org/jeps/jep-0163.html Personal Eventing Protocol (JEP-0163)]. | * 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)]. | ||
* Handle several JIDs through one connection | |||
== Links == | |||
[http://jabberd.jabberstudio.org/dev/docs/component.shtml Jabberd2's component protocol] | |||
== Current discussions == | |||
The most likely approach to improve the protocol is: | |||
* First define a simple API of target operations. | |||
* Propose an XMPP formalism for the API using "adhoc commands" that cna be handled by the server. | |||
One of the first target in the API is roster item addition (with nickname and subscription) and deletion. | |||
== Restriction to remove == | |||
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. | |||