From 99194d9a46b8f9d738ee90dc2ecc5ba4dfeedbe7 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 9 Jun 2008 17:27:53 +0000 Subject: [PATCH] updated examples per XEP-0115 git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1931 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0163.xml | 23 ++++++++++++----------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/xep-0163.xml b/xep-0163.xml index 08214950..5bf51d3f 100644 --- a/xep-0163.xml +++ b/xep-0163.xml @@ -268,9 +268,10 @@ - + ]]>

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:

@@ -397,18 +398,18 @@

As mentioned, a PEP service MUST send the last published item to all new subscribers and to all newly-available resources for each subscriber, including the account owner itself. (That is, the default value of the "pubsub#send_last_published_item" node configuration field must be "on_sub_and_presence"; this behavior essentially mimics the functionality of presence as defined in XMPP IM.)

- + ]]> - + ]]>