Dave, Personally I'm all for the client specifically request last items from a node after a capability change, that way it isn't a forced behaviour (lower possibly wasted bandwidth) and also we don't have to get into a conversation about how many latest items to send ? (perhaps just the last 1 item on it's own doesn't make sense, eg. Collaboration events or similar ?)
Just my opinion Kirk On 17 Jul 2010, at 06:46, Dave Cridland <[email protected]> wrote: > On Fri Jul 16 16:27:38 2010, Christophe Romain wrote: >> So, updating capabilities enable or disable PEP events you may receive >> by implicit or explicit subscription. But i don't think you should get >> the last published item in that case. Caps are just kind of filter. >> By the way, when clients enables a new capabilities, it can also >> ask pubsub for last published items on related nodes. > > Well, yes, but... > > When would a client turning on a capability not want the last item? > > FWIW, I think M-Link will send last published item if a capability change > produces a newly unfiltered node. > > Then again, I wasn't intending to filter manual subscriptions, either, yet > the spec implies that I should. > > I'm not against changing either of these, but it feels intuitively incorrect. > > Dave. > -- > Dave Cridland - mailto:[email protected] - xmpp:[email protected] > - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/ > - http://dave.cridland.net/ > Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade
