On Fri, Sep 18, 2009 at 02:57:18PM -0600, Peter Saint-Andre wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > A few months ago I had an IM chat with Brian Cully about the > include_body option. As Brian pointed out, this is the only > subscription-related configuration option that results in modification > of the event notification (by either including or not including the XMPP > message <body/> element). However, this doesn't play nicely with the > multi-subscribe option, because it's unclear what the pubsub service > should do if one of the subscriptions specifies include_body = true and > another subscription specifies include_body = false (does it send two > notifications, one with body and one without?). > > Options: > > 1. Get rid of include_body > > 2. Better specify handling > > 2a. Send multiple notifications and let the client remove dups > > 2b. Say that include trumps don't include, and include the body > > 3. Other?
I would say 2b, but 1 also works for me. I am not sure why any notification would need a body. If an entity subscribed to a node (let's say including a resource), I expect that the entity can actually process the notifications. If another resourve would receive a notification, I expect that entity to want to drop the message entirely and not bother the user. -- Groetjes, ralphm
