40
edits
Difference between revisions of "PubSubIssues"
Jump to navigation
Jump to search
→XEP-0060: PubSub
| (One intermediate revision by the same user not shown) | |||
| Line 4: | Line 4: | ||
Note: these issues are keyed to the section numbers in version 1.13 of XEP-0060. | Note: these issues are keyed to the section numbers in version 1.13 of XEP-0060. | ||
=== Temporary Subscriptions is not discoverable (Section 12.4) === | |||
http://xmpp.org/extensions/xep-0060.html#impl-tempsub describes temprary subscriptions for a pub/sub node. It is not mentioned anywhere in the XEP-0060 how to discover this feature (pubsub#tempsub). | |||
=== Affiliation Change Notifications (Section 8.9.4) === | === Affiliation Change Notifications (Section 8.9.4) === | ||
| Line 27: | Line 33: | ||
Would be good if the PubSub spec would have a reference to the service discovery error conditions if a disco request is send to a non existent node. I've reports from users that some implementations return a non-error result, which e.g. results in Smack returning a NotAPubSubNodeException instead of a XMPPErrorException (which is what most would expect). So it's not clear for some implementors what do in this case (which is likely because the relevant information is found in a different XEP). | Would be good if the PubSub spec would have a reference to the service discovery error conditions if a disco request is send to a non existent node. I've reports from users that some implementations return a non-error result, which e.g. results in Smack returning a NotAPubSubNodeException instead of a XMPPErrorException (which is what most would expect). So it's not clear for some implementors what do in this case (which is likely because the relevant information is found in a different XEP). | ||
=== Optional redirect URI for <delete/> not discoverable (Section 8.4) === | |||
Server support for <redirect/> is optional for servers, yet clients have no way of discovering if the server supports it. Also, it doesn't state the maximum number of <redirect/> elements allowed, although it seems to suggest it's one. Proposed solution: | |||
* Add feature delete-nodes-redirect (OPTIONAL) | |||
* Modify language to state there can be only one redirect element. | |||
== XEP-0163: PEP == | == XEP-0163: PEP == | ||