From f443d29bc924b44705d11bbe6fb47c6a1e63192a Mon Sep 17 00:00:00 2001 From: Florian Schmaus Date: Mon, 12 Mar 2018 15:45:58 +0100 Subject: [PATCH] XEP-0163: Clarify how +notify works MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It sounded like annoucing the jabber.org/protocol/foo+notify feature causes one to receive notifications from *all* nodes related to the jabber.org/protocol/foo protocol, but as per XEP-0060 § 9.2, one will only receive notifications of the node whose NodeID equals 'jabber.org/protocol/foo'. --- xep-0163.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0163.xml b/xep-0163.xml index 7fc0fbca..88380866 100644 --- a/xep-0163.xml +++ b/xep-0163.xml @@ -280,7 +280,7 @@ ver='zHyEOgxTrkpSdGcQKH8EFPLsriY='/> ]]> -

Your server knows to send tune information to Romeo because when the server unpacks the value of the 'ver' attribute ("054H4A7280JuT6+IroVYxgCAjZo=") in accordance with XEP-0115, it discovers that Romeo's client advertises a service discovery feature of "http://jabber.org/protocol/tune+notify", where the "+notify" suffix indicates interest in receiving notifications related to the protocol that precedes the suffix. The server can verify this support if needed by sending a service discovery request to Romeo's full JID, where the response would be as follows:

+

Your server knows to send tune information to Romeo because when the server unpacks the value of the 'ver' attribute ("054H4A7280JuT6+IroVYxgCAjZo=") in accordance with XEP-0115, it discovers that Romeo's client advertises a service discovery feature of "http://jabber.org/protocol/tune+notify", where the "+notify" suffix indicates interest in receiving notifications of the node whose NodeID precedes the suffix (see XEP-0060 § 9.2). The server can verify this support if needed by sending a service discovery request to Romeo's full JID, where the response would be as follows: