Difference between revisions of "PubSubIssues"

Jump to navigation Jump to search
125 bytes added ,  11:37, 17 October 2014
 
Line 24: Line 24:
* Section 7.1.2.3 says: "If configured to do so, the service can include the publisher of the item when it generates event notifications." but there is no way to configure this bevahiour described. Probably need to add appropriate discovery feature + configuration form item.
* Section 7.1.2.3 says: "If configured to do so, the service can include the publisher of the item when it generates event notifications." but there is no way to configure this bevahiour described. Probably need to add appropriate discovery feature + configuration form item.


=== Expected response to disco info and disco items request to a non existing node is not specified (Section 5.3 and 5.5) ===
=== Expected response to disco info and disco items request to a non existing node (Section 5.3 and 5.5) ===


It is not specified what the PubSub service should return if the client performs a disco info or disco items request on a non-existent PubSub 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).
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).


== XEP-0163: PEP ==
== XEP-0163: PEP ==
163

edits

Navigation menu