> From: [email protected]
> To: [email protected]
> Date: Tue, 17 Nov 2009 13:23:00 +0100
> Subject: Re: [PubSub] Pubsub and node meta-data
>
> On Sun, 2009-11-08 at 20:48 +0800, Brett Zamir wrote:
> > On 11/8/2009 5:26 PM, Peter Saint-Andre wrote:
> > > On 10/2/09 12:46 AM, Brett Zamir wrote:
> > >
> > >> While attributes are being added to<item/>, would there also be some
> > >> way to add meta-data about the node to the event as well, e.g.,
> > >> pubsub#num_subscribers (the number of subscribers to the node) or
> > >> pubsub#title (human-readable node name)? I know it can be retrieved
> > >> separately, but this seems it could be useful to be able to get back
> > >> together...
> > >>
> > > I don't see the logic of this -- you want to include meta-data about the
> > > node in an element that has information about a specific item?
> > >
> >
> > I don't think it makes sense as a part of <item/> (nor as part of the
> > payload within <item/>) but a sibling of the <event/> in the <message/>
> > that delivers the item.
>
> I disagree. If you want any kind of additional meta-data sent along with
> a notification, at the level you describe, you can use SHIM headers for
> that. That said, for now I think this is really application specific. If
> it should become specified in a XEP at some point, which I doubt, this
> can easily be put in a new XEP, not in XEP-0060.
>
> As for creating new node or subscription configuration settings to
> toggle this, you are free to use your own fields in the form, as long as
> the name starts with 'x-', as specified in XEP-0068, section 3.4.
>
I agree, this seems like a reasonable way to accomplish this without
any changes or additions to the spec.
> ralphm
>
>
_________________________________________________________________
Windows Live: Friends get your Flickr, Yelp, and Digg updates when they e-mail
you.
http://go.microsoft.com/?linkid=9691817
