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

Peter Saint-Andre stpeter at jabber.org
Mon Jan 30 23:09:51 UTC 2006


-----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.

P


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

iD8DBQFD3py/NF1RSzyt3NURAg4OAJ9x3+CI5PXUFzeiyjpS+BwcF6uSpwCg4OKc
nSP+ETNTAJnlW34Looy1Qgc=
=OF/v
-----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/38f91708/attachment.bin>


More information about the Standards mailing list