[Standards-JIG] JEP-0060 Publisher Model - node hirarchy permissions

Brian Raymond brian.raymond at je.jfcom.mil
Thu May 25 16:06:22 UTC 2006




On 5/25/06 11:15 AM, "bernhard" <bz at datenkueche.com> wrote:

> Hi
>> Your example is correct.
>>   
> ;-)
>> I don't understand what you mean by 'moving' nodes. It might be that you
>> refer to changing the hierarchy in the node names. Then you are in for a
>> surprise: node ids are opaque. The fact that some implementations make
>> it seem like there is any hierarchy by using '/' inside node ids doesn't
>> help.
>>   
> If I have a request like:
> <iq type="get" to="pubsub.jaim.at" id="nodelist"><query
> xmlns="http://jabber.org/protocol/disco#items"
> node="home/jaim.at/pubsub"/></iq>
> 
> I get a response with "nodes" and "items" that are children of
> "home/jaim.at/pubsub"
> If a node is a parent and the other is a child there is a hierarchy.
> Nodes can have child nodes and they again can have child nodes. ->tree
> (I don't talk about items)
> Use PSI Service Discovery:
> server: jaim.at
> node: home/jaim.at/pubsub
> There you can see the tree.
> 
> What is the "id" of a node?

In this case the node id is "home/jaim.at/pubsub". The ids used here imply a
hierarchy however PubSub itself doesn't know of any relationship between the
nodes unless collection nodes are used and child nodes are configured with
"pubsub#collection".  If you have collection nodes you could "move" them to
a new parent by configuring it as you demonstrated in an earlier email.

> 
> 
> thanks
> 
> Bernhard



More information about the Standards mailing list