On Sep 29, 2009, at 5:53 AM, Dave Cridland <[email protected]> wrote:
On Tue Sep 29 12:31:39 2009, Mads Randstoft wrote:
After some talks at the jabber dev MUC, it seems there is a need to
be
able to add more data to a node and more data to an item than is
currently possible in a std. way.
I see priority as a valid addition to pubsub queuing. As far as
metadata is concerned, this seems to be contextual to the service
provider, and there is no way for a 3rd party pubsub service to
interpret your metadata, and so it is an implementation detail. Are
there values you need outside of the spec? Then add your own namespace
for your values to the publish call inside the pubsub element. If you
think these values would be helpful to others, get them added to an
appropriate xep or see if there is interest in a new xep
-Nathan Fritz (cellphone)
Right, specifically, we've seen developer interest in both priority
(as some nebulous thing) and in timestamps.
I think we could reasonably have a concept of some metadata
container element which has some stuff in - which the pubsub service
and subscribers may or may not do things with. The metadata
container element can be independent of the payload.
I don't know where this might fit, but I'd assume a pubsub service
would have to support metadata, and a subscriber would have to
request it as a subscription option.
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
