Difference between revisions of "XEP-Remarks/XEP-0060: PubSub"
Jump to navigation
Jump to search
(Created page with "= Missing functionality = XEP-60 appears to be missing some important use cases, so that some implementations have to resort to using their own flavor of PubSub, e.g. Buddyclo...") |
|||
| Line 1: | Line 1: | ||
= Missing functionality = | = Missing functionality = | ||
XEP-60 appears to be missing some important use cases, so that some implementations have to resort to using their own flavor of PubSub, e.g. Buddycloud. Which prevents those projects from using standard compliant PubSub implementations (e.g. Buddycloud uses a patched version of Smack's PubSub implementation). | XEP-60 appears to be missing some important use cases, so that some implementations have to resort to using their own flavor of PubSub, e.g. Buddycloud. Which prevents those projects from using standard compliant PubSub implementations (e.g. Buddycloud uses a patched version of Smack's PubSub implementation). | ||
Examples include | |||
* Adding a new access model 'local'. See [http://buddycloud.github.io/buddycloud-xep/#default-roles Buddycloud-XEP: Channel Access Models] vs. [http://www.xmpp.org/extensions/xep-0060.html#accessmodels XEP-60 4.5 Node Access Models] | |||
Revision as of 08:43, 18 December 2014
Missing functionality
XEP-60 appears to be missing some important use cases, so that some implementations have to resort to using their own flavor of PubSub, e.g. Buddycloud. Which prevents those projects from using standard compliant PubSub implementations (e.g. Buddycloud uses a patched version of Smack's PubSub implementation).
Examples include
- Adding a new access model 'local'. See Buddycloud-XEP: Channel Access Models vs. XEP-60 4.5 Node Access Models