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

Peter Saint-Andre stpeter at jabber.org
Thu Feb 2 21:20:38 UTC 2006


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

Jacek Konieczny wrote:
> On Mon, Jan 30, 2006 at 04:09:51PM -0700, Peter Saint-Andre wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Kevin Smith wrote:
>>> On 30 Jan 2006, at 22:28, Peter Saint-Andre wrote:
>>>> 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 there a reason for them not to be musts?
>> Backwards compatibility with older implementations, mostly.
> 
> IMHO that should be _at most_ SHOULD in the PubSub specification -- for not
> SPPS uses it may be not needed, add complicates things.  The requirement
> should be raised by SPPS specification to MUST, though.

So it shall be.

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

iD8DBQFD4nemNF1RSzyt3NURAtoUAJ4o8jCWPj2us9vUaRuTrSbqhZUt1QCgmRi8
4J39cd7X4/9Z++shuHRccss=
=Tk8v
-----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/20060202/cf21a8a0/attachment.bin>


More information about the Standards mailing list