From 09df50be60307d72759908ceed6ceb34c1114b4f Mon Sep 17 00:00:00 2001 From: stpeter Date: Tue, 28 Feb 2012 12:49:56 -0700 Subject: [PATCH] 0.0.1 --- inbox/pubsub-since.xml | 106 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 106 insertions(+) create mode 100644 inbox/pubsub-since.xml diff --git a/inbox/pubsub-since.xml b/inbox/pubsub-since.xml new file mode 100644 index 00000000..07733f02 --- /dev/null +++ b/inbox/pubsub-since.xml @@ -0,0 +1,106 @@ + + +%ents; +]> + + +
+ PubSub Since + This specification defines a publish-subscribe feature that enables a subscriber to automatically receive pubsub and PEP notifications since its last logout time. + &LEGALNOTICE; + xxxx + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + + + + NOT_YET_ASSIGNED + &hildjj; + &stpeter; + + 0.0.1 + 2012-02-27 + psa +

First draft.

 + +
+ + +

Many &xep0060; and &xep0163; services send notifications based on information about the presence of subscribers. This implies that subscribers might not receive notifications that were generated when they are offline at a particular resource. While &xep0256; defines a way for clients to include their last logout time, this specification closes the loop by defining how pubsub and PEP services can use the last logout information to send interim notifications to subscribers.

+ + + +

As described in XEP-0256, a subscriber can indicate its last logout time when sending initial presence.

+ + + + ]]> +

Upon receiving such an indication, a pubsub or PEP service that supports presence-based notifications and the "pubsub-since" feature defined herein would behave as follows:

+
    +
  1. The service MUST send to the subscriber all of the notifications stored in the relevant node's history that were generated since the last logout time.
    2. +
  2. The service MAY adjust its definition of "interim notification" to account for reasonable clock skew (e.g., including notifications up to five minutes older than the subscriber's last logout time).
    3. +
  3. The service SHOULD include only the final version of each pubsub notification (e.g., in case of items that were updated during the period when the subscriber was offline).
    4. +
  4. The service SHOULD NOT include items that were removed from the node.
    5. +
  5. The service MAY limit the number of notifications that it sends to avoid resource contraints.
    6. +
  6. The service MAY include &xep0059; data so that the subscriber can page through the set of interim notifications.
    7. +
+ + + +

If a pubsub or PEP service supports the protocol defined herein, it MUST report that by including a &xep0030; feature of "http://jabber.org/protocol/pubsub#since" in response to disco#info requests:

+ + + + ]]> + + + + + + + + + + ]]> + + + +

The number or cumulative size of the notifications published since the subscriber's last login time might be large, causing a significant load on the service. Implementations might consider truncating the interim notifications to avoid a denial of service.

+ + + +

This document requires no interaction with &IANA;.

+ + + + +

Support for the feature defined in this document is advertised by the ""http://jabber.org/protocol/pubsub#since"" Service Discovery feature.

+

The XMPP Registrar shall add this feature to its registry at &DISCOFEATURES;. The registration is as follows.

+ + http://jabber.org/protocol/pubsub#since + + The pubsub or PEP service sends interim notifications upon receiving + initial presence containing the subscriber's last logout time. + + XEP-xxxx + + ]]> + + + +