22
edits
Difference between revisions of "PubSubIssues"
Jump to navigation
Jump to search
→No text on #publish_model
| (5 intermediate revisions by one other 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. | |||
=== Redundant features for Item Retraction === | |||
The latest revision introduced a feature 'delete-items', while 'retract-items' was already there. Ralphm proposed to the list: | |||
<blockquote> | |||
[...] Reading the text around it, I feel it is | |||
confusing, too. I'd rather go with talking about 'retracting items' and | |||
'deleting nodes' thoughout, and not talk about 'deleting items'. | |||
</blockquote> | |||
<blockquote> | |||
I think that many (all?) clients ignore this feature for discovery | |||
altogether, so what about making 'delete-items' a thing that servers | |||
SHOULD also advertise along with 'retract-items', but have clients | |||
depend on 'retract-items' exclusively? | |||
</blockquote> | |||
=== No text on #publish_model === | |||
A few examples mention an option #publish_model, which seems useful, but there's no actual text describing behaviour of said option. | |||
=== Entity node creation authorization request (Section 8.1) === | |||
There's no way to know if an entity can create (or not) a node before actually create it. | |||
This issue bring a bad UI experience on some Pubsub clients (we display an error after the form creation submission). | |||
== XEP-0163: PEP == | == XEP-0163: PEP == | ||