[Standards-JIG] pubsub tracking proto-JEP

Bob Wyman bob at wyman.us
Mon Feb 6 21:00:56 UTC 2006


Peter Saint-Andre wrote on 12-Dec-2005:
> FYI, Magnus Henoch has sent me a new version of the pubsub tracking 
> proto-JEP:
> http://www.jabber.org/jeps/inbox/pubsub-tracking.html 
	My apologies for responding so slowly...

	It strikes me that this proto-JEP is unnecessary. What we do at
PubSub.com is support discovery of outstanding subscriptions via an
affiliations query. This seems adequate to solve the problem addressed by
the proto-JEP. See:
http://www.pubsub.com/docs/pubsub_xmpp_draft.html#DiscoveringExistingSubscri
ptions

Examples follow:

Client Requests Current Affiliations:

C: <iq type="get"
       from="sample_at_pubsub_dot_com at xmpp.pubsub.com"
       to='xmpp.pubsub.com"
       id="allsubs">
     <pubsub xmlns="http://jabber.org/protocol/pubsub">
       <affiliations/>
     </pubsub>
   </iq>

Server Returns Current Affiliations:

S: <iq id="allsubs" type="result" from="xmpp.pubsub.com">
  <pubsub xmlns="http://jabber.org/protocol/pubsub">
    <affiliations>
      <entity  
        node="pubsub/topics/101" 
        subid="pubsub/subs/71304ce006a02c5049b63cb142c9b11e" 
        jid="sample_at_pubsub_dot_com at xmpp.pubsub.com" 
        affiliation="none" 
        subscription="subscribed"/>
      <entity node="pubsub/topics/101" 
        subid="pubsub/subs/66271d2e70372c1b4dc5b46e79a6f001" 
        jid="sample_at_pubsub_dot_com at xmpp.pubsub.com" 
        affiliation="none" 
        subscription="subscribed"/>
    </affiliations>
  </pubsub>
</iq>






More information about the Standards mailing list