From e9668e88f8deedea7e1828d06272cb63fc7d4142 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Mon, 3 Mar 2008 16:27:11 +0000 Subject: [PATCH] typo git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1720 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0222.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0222.xml b/xep-0222.xml index 28e538e0..3c82793c 100644 --- a/xep-0222.xml +++ b/xep-0222.xml @@ -100,7 +100,7 @@

Your publish request is a standard pubsub request except that:

  1. The item is persisted (pubsub#persist_items is true).
    2. -
  2. The last published item is never sent (pubsub#last_published_item is set to "never" so that items are pushed out only when modified).
    3. +
  3. The last published item is never sent (pubsub#send_last_published_item is set to "never" so that items are pushed out only when modified).

(In this case, access is limited to people in your Friends roster group.)

If all goes well (see Publishing an Item), your key will be pushed out to all appropriate individuals (in this case only Romeo). In particular, Romeo receives your key because he has auto-subscribed to the virtual pubsub service at your bare JID via a presence subscription and because his &xep0115; data indicated that he is interested in the "urn:xmpp:tmp:pubkey" payload type.

@@ -178,7 +178,7 @@

The best practices described herein re-use the concepts already defined in XEP-0060 and XEP-0163. In order to optimize for object persistence instead of transient event notifications, a node MUST be configured as follows:

  1. Set pubsub#persist_items to true.
    2. -
  2. Set pubsub#last_published_item to "never".
    3. +
  3. Set pubsub#send_last_published_item to "never".

The access model MAY be any model defined in XEP-0060.