-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/16/09 4:29 PM, Peter Saint-Andre wrote:
> On 8/5/09 1:42 PM, Michael Jakl wrote:
>> Hi!
>
>> A small note:
>> Example 24. talks about querying for the node "princely_musings", but
>> the related (answer) exmple 25. talks about "node6".
>
> It seems I fixed that at some point...
>
>> Is there a specific reason that "5.7 Retrieve Affiliations" doesn't
>> follow the same path and also supports the retrieval of the user's
>> affiliation for a specific node?
>
> Would that be a helpful feature? It would be quite easy to add it.
I've added an example of this to my working copy...
***
In order to make an affiliations request of a specific node, the
requesting entity includes an empty <affiliations/> element with a
'node' attribute.
Example 30. Entity requests affiliation at a specific node
<iq type='get'
from='[email protected]/barracks'
to='pubsub.shakespeare.lit'
id='affil2'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<affiliations node='node6'/>
</pubsub>
</iq>
Example 31. Service replies with current affiliation
<iq type='result'
from='pubsub.shakespeare.lit'
to='[email protected]'
id='affil2'>
<pubsub xmlns='http://jabber.org/protocol/pubsub'>
<affiliations node='node6'>
<affiliation node='node6' affiliation='owner'/>
</affiliations>
</pubsub>
</iq>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkqxbjUACgkQNL8k5A2w/vwC0QCfZTpxGgReu/1f1HDx4tqTZW6K
F1gAoJpt8ppiefMNkCJAiOyyqSY+4Lhi
=XGST
-----END PGP SIGNATURE-----
