1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-30 21:22:15 -05:00

Merge commit 'refs/pull/604/head' of https://github.com/xsf/xeps into feature/xep-0163

This commit is contained in:
Jonas Wielicki 2018-03-18 12:16:08 +01:00
commit 91209ff312

View File

@ -280,7 +280,7 @@
ver='zHyEOgxTrkpSdGcQKH8EFPLsriY='/> ver='zHyEOgxTrkpSdGcQKH8EFPLsriY='/>
</presence> </presence>
]]></example> ]]></example>
<p>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 <cite>XEP-0115</cite>, 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:</p> <p>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 <cite>XEP-0115</cite>, 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 <cite>XEP-0060 § 9.2</cite>). 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:</p>
<example caption='Disco#info result from extension'><![CDATA[ <example caption='Disco#info result from extension'><![CDATA[
<iq from='romeo@montague.lit/orchard' <iq from='romeo@montague.lit/orchard'
to='juliet@capulet.lit' to='juliet@capulet.lit'