[ejabberd] PubSub node names and ejabberd

Mickaël Rémond mickael.remond at process-one.net
Sat Nov 22 12:05:42 MSK 2008

We are open to discuss why did this with a good reason with the writer  
of the spec and open to help improve the spec based on our real world  

Mickael Remond

Le 22 nov. 08 à 01:12, Jack Moffitt <jack at chesspark.com> a écrit :

>> Yes, but we are using a semantic for a good reason. Without a way  
>> to filter
>> node a good default behaviour is to have a hierarchy to order a  
>> large number
>> of nodes.
> Maybe so, but this probably means that the hierarchy and spec
> violation should be something people opt into, not the default
> behavior.  I don't see why you need a hierarchy in the node names,
> when a hierarchy is implicit in the leaf/collection relationships.
> ejabberd's default implementation means that people using examples
> from the spec will find that they don't work.  Also, why is there a
> '/home'?  Wouldn't the root of the tree just be '/'.
> jack.
> _______________________________________________
> ejabberd mailing list
> ejabberd at jabber.ru
> http://lists.jabber.ru/mailman/listinfo/ejabberd

More information about the ejabberd mailing list