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

Jacek Konieczny jajcus at jajcus.net
Tue Jan 31 08:33:10 UTC 2006


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.

Greets,
        Jacek



More information about the Standards mailing list