[standards-jig] pubsub affiliations

Justin Kirby justin at openaether.org
Fri Jun 13 09:47:50 UTC 2003


in 7.1.5 current affiliations, it shows how to get *all* current
affiliations for *all* nodes.  

Should there be an option to filter on a node?  And if so then whats the
difference from the <entities node="42"/>  ?

So then that leads me to what is the value/purpose of <affiliation/>
other than a specific entity request? Wouldn't it be more consistent to
move the affiliation request feature into the <entity/> ?

To get *all* affiliations with *all* nodes:

<iq type="get" from="sub1 at foo.com" to="pubsub.jabber.org" id="allsubs">
  <pubsub xmlns="http://jabber.org/protocol/pubsub">
    <entities/>
  </pubsub>
</iq>


Response:

<iq type="result" to="sub1 at foo.com" from="pubsub.jabber.org" id="allsubs">
  <pubsub xmlns="http://jabber.org/protocol/pubsub">
    <entities>
      <entity node="node1" jid="sub1 at foo.com"
              affiliation="owner" subscription="subscribed"/>
      <entity node="node2" jid="sub1 at foo.com"
              affiliation="publisher" subscription="subscribed"/>
      <entity node="node3" jid="sub1 at foo.com/pda"
              affiliation="none" subscription="unconfigured"/>
      <entity node="node4" jid="sub1 at foo.com/work"
              affiliation="none" subscription="pending"/>
      <entity node="node5" jid="sub1 at foo.com"
              affiliation="outcast" subscription="none"/>
      <entity node="node6" jid="sub1 at foo.com"
              affiliation="owner" subscription="none"/>
    </entities>
  </pubsub>
</iq>



Thoughts?

Justin




More information about the Standards mailing list