[Psi-devel] Re: x:data not working to ejabberd server

[Trejkaz]

On Mon, 17 Jan 2005 05:46, Magnus Henoch wrote:
> Michail Pishchagin <mblsha-psi at affinix.com> writes:
> > It's because ejabber's configuration is not defined in any standard
> > (basically it's a small hack that uses custom xmlns to request the
> > data form). And tkabber supports it because it's from the same
> > author ;)
> >
> > It needs to be modified to use the ad-hoc commands ;)
>
> ejabberd:config does have redeeming qualities compared to ad-hoc
> commands.  In particular, it allows commands to be organized in a tree
> through normal disco, instead of the flat list that ad-hoc commands
> offers.
>
> Then again, standardized protocols are a good thing...

What's wrong with combining the two approaches?

I see no reason why I can't go into the Service Discovery dialog, navigate 
through a tree of commands, then right-click and choose "Execute Command".  
Well, except that Psi can't do it yet, of course.  But still, it's reasonably 
intuitive.

Something makes me wonder whether it's considered acceptable for a node of 
type "command-list" to contain further nodes of type "command-list", in this 
case.  With something like a server, there are clearly _way_ too many 
commands to present in a single drop-down box.

TX

-- 
             Email: Trejkaz Xaoza <trejkaz at trypticon.org>
          Web site: http://xaoza.net/
         Jabber ID: trejkaz at jabber.zim.net.au
   GPG Fingerprint: 9EEB 97D7 8F7B 7977 F39F  A62C B8C7 BC8B 037E EA73
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
Url : http://listserver.dreamhost.com/pipermail/psi-devel-affinix.com/attachments/20050117/1c550909/attachment.bin