On Sat, Jul 17, 2010 at 10:46 AM, 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? >
+1. > FWIW, I think M-Link will send last published item if a capability change > produces a newly unfiltered node. > Prosody does the same. It was the logical thing to do. > 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. -- Waqas
