[Standards-JIG] pubsub: cache-last-item

Peter Saint-Andre stpeter at jabber.org
Mon Jan 30 22:28:28 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I want to make sure that the proposed "cache-last-item" functionality is
clearly understood before we move forward with revisions to JEP-0060. My
understanding from the list discussion last fall was this:

1. Even if a node or service is not configured to support item
persistence, it SHOULD cache the last item published to each node.

   Question: should this be MUST?

2. When a subscription is accepted/approved, the service SHOULD send the
last published item to the new subscriber.

   Question: should this be MUST?

Is this consistent with our discussion last fall?

Note that this obviates the need for a "subscribe-and-get-last-item"
feature.

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFD3pMLNF1RSzyt3NURAnTpAJj9WsvMN0O9tLr784Iv4q6Dx8yUAJ4jsHZv
JRkuSaOCHjmvObs0kuKq0w==
=sZun
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060130/b81e15bd/attachment.bin>


More information about the Standards mailing list