On 6/11/07, Olivier Goffart <[EMAIL PROTECTED]> wrote:
And i would even put the body element in the root of the message element. So
even client that doesn't support pubsub can receive such message
Hmm... I disagree here a bit, but of course, you're the developer, so
the final decision is always yours ;) Here are my reasons:
1) It's not standard compliant I believe: every pubsub event is a
subchild of <event> field (at least I think this looking at XEP-0060
examples), so you can't go out of this field anyway without breaking
the protocol
2) We want (at least, me :) PEP protocols to spread, so I believe it
would be a bad idea to let it be granted (after all, it's not a
message, it's not a presence, but something in between, probably
closer to presence but not that close)
3) Personally I'd like to see it through knotify/growl, and not a
message - since it would be hard to tell if user typed it in or it is
just automatic eventing from AmaroK. Example:
http://jabbermania.blogspot.com/2007/05/general-pubsub-pep-receiver.html
Look at the picture (mockup of knotify).
Of course it's only my personal taste, but differentiating eventing
protocols from standard messages is a feature I believe.
(and for all PUBSUB stuff)
(Client will not receive it if there is no tune+notify feature. But the user
may still request the notification using the normal pubsub subscription ? )
<message
from='[EMAIL PROTECTED]'
to='[EMAIL PROTECTED]'>
<event xmlns='http://jabber.org/protocol/pubsub#event'>
<items node='http://jabber.org/protocol/tune'>
<item id='bffe6584-0f9c-11dc-84ba-001143d5d5db'>
<tune xmlns='http://jabber.org/protocol/tune'>
<artist>Yes</artist>
<length>686</length>
<source>Yessongs</source>
<title>Heart of the Sunrise</title>
<track>3</track>
<uri>http://www.yesworld.com/lyrics/Fragile.html#9</uri>
</tune>
</item>
</items>
</event>
<body>Peter is listening to: Yessongs - Heart of the Sunrise</body>
</message>
--
Aadaam <[EMAIL PROTECTED]>
