moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-28 04:02:20 -05:00
Code Issues Releases Wiki Activity

0.2

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3643 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-11-18 18:48:54 +00:00
parent c4f186b323
commit 5b5048be87
1 changed files with 23 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
xep-0253.xml
View File

@ -24,6 +24,12 @@
<shortname>NOT_YET_ASSIGNED</shortname> <shortname>NOT_YET_ASSIGNED</shortname>
&ralphm; &ralphm;
&stpeter; &stpeter;
<revision>
<version>0.2</version>
<date>2009-11-18</date>
<initials>psa</initials>
<remark><p>Specifed protocol flow for the chained subscription.</p></remark>
</revision>
<revision> <revision>
<version>0.1</version> <version>0.1</version>
<date>2008-11-13</date> <date>2008-11-13</date>
@ -136,11 +142,25 @@
status='completed'/> status='completed'/>
</iq> </iq>
]]></example> ]]></example>
<p>At this point, the service itself will subscribe to the remote node.</p>
<example caption='Service subscribes to remote node for chaining'><![CDATA[
<iq type='set'
from='weatherbot@consumer.tld/Chicagoland'
to='notify.weather.tld'
id='sub1'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<subscribe
node='OHR'
jid='weatherbot@consumer.tld/Chicagoland'/>
</pubsub>
</iq>
]]></example>
<p>Now subscribers who are local to the consumer.tld XMPP service can subscribe directly to weatherbot@consumer.tld/Chicagoland instead of the remote pubsub node at notify.weather.tld. We therefore refer to weatherbot@consumer.tld/Chicagoland as a "chaining node" and the remote node as a "chained node".</p>
</section1> </section1>
<section1 topic='Notifications' anchor='notifications'> <section1 topic='Notifications' anchor='notifications'>
<p>When a chained pubsub node delivers notifications to its subscribers, it SHOULD include an &xep0033; header of "ofrom" (note: this header is not yet defined in <cite>XEP-0033</cite>).</p> <p>When a chaining node delivers a notification to its subscribers, it SHOULD include an &xep0033; header of "ofrom" to specify the chained node or service that generated the notification (note: this header is not yet defined in <cite>XEP-0033</cite>).</p>
<example caption='Service notifies subscribers'><![CDATA[ <example caption='Chaining node notifies subscribers'><![CDATA[
<message from='weatherbot@consumer.tld/bot' <message from='weatherbot@consumer.tld/bot'
to='subscriber@consumer.tld' to='subscriber@consumer.tld'
id='foo'> id='foo'>
@ -181,7 +201,7 @@
<code caption='Registry Submission'><![CDATA[ <code caption='Registry Submission'><![CDATA[
<form_type> <form_type>
<name>http://jabber.org/protocol/pubsub#chaining</name> <name>http://jabber.org/protocol/pubsub#chaining</name>
<doc>XEP-xxxx</doc> <doc>XEP-0253</doc>
<desc>Forms used for chaining of pubsub nodes.</desc> <desc>Forms used for chaining of pubsub nodes.</desc>
<field var='local-node' <field var='local-node'
type='text-single' type='text-single'