[jdev] PubSub subscription stanzas
Jonathan Dickinson
jonathan.dickinson at k2.com
Thu Oct 9 12:32:16 CDT 2008
Hey julien,
I know this has nothing to do with your question (i will read the spec tomorrow if somebody doesn't beat me to it), take more care about exposing your email on public mailing lists :), spambait.
Sent from my Windows Mobile® phone.
________________________________
From: Julien Genestoux <julien.genestoux at gmail.com>
Sent: 09 October 2008 07:28 PM
To: jdev at jabber.org <jdev at jabber.org>
Subject: [jdev] PubSub subscription stanzas
Hi everyone,
I am currently working on a project that involves a XMPP PubSub mechanism.
I am trying to implement a component that will manage this since we don't want to use a "full" PubSub server.
Our users will be able to subscribe to a source using both a XMPP client and our web application.
When a user subscribes to a node using the XMPP client, it is easy, I just have to follow what's given here : http://xmpp.org/extensions/xep-0060.html#subscriber-subscribe
However, when he subscribes from our web application, what kind of stanza should I send, since the request is not coming from the xmpp client itself? My idea was to send something like :
<iq type='result'
from='pubsub.shakespeare.lit'
to='francisco at denmark.lit/barracks'
id='sub1'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<subscription
node='princely_musings'
jid='francisco at denmark.lit'
subid='ba49252aaa4f5d320c24d3766f0bdcade78c78d3'
subscription='subscribed'/>
</pubsub>
</iq>
But the 'result' in iq type feels weird, since my understdanding was that resul corresponds to an action that was led by the client? Am I wrong? If so, can I send something like type='set' ?
Thanks,
--
Julien Genestoux
julien.genestoux at gmail.com<mailto:julien.genestoux at gmail.com>
http://www.ouvre-boite.com
Notifixious : http://tinyurl.com/notifixious
+1 (415) 254 7340
+33 (0)8 70 44 76 29
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20081009/91b259b5/attachment-0003.htm>
More information about the JDev
mailing list