iq:browse: <a href="http://www.xmpp.org/extensions/xep-0011.html">http://www.xmpp.org/extensions/xep-0011.html</a><br>iq:agents: <a href="http://www.xmpp.org/extensions/xep-0094.html">http://www.xmpp.org/extensions/xep-0094.html
</a><br><br>Both seem pretty simple, but both are depreciated.<br><br>I know pandion (<a href="http://www.pandion.be/">http://www.pandion.be/</a>) uses iq:browse to find services that are available.<br><br>So is it possible to implement hooks that other plugins can tie into to implement iq:browse? or is this something that has to be done through core?
<br><br>Gavin<br><br><div><span class="gmail_quote">On 4/15/07, <b class="gmail_sendername">Martin Atkins</b> <<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Gavin Mogan wrote:<br>> So apparently the MUC plugin works pretty well. I still was unable to<br>> get the external component to work.<br>><br>> I have noticed that with the 4 or 5 main windows clients, half support
<br>> the disco service discovery properly (i have a MUC patch to make things<br>> work better), the other half uses the depreciated iq:browse and iq:agents.<br>><br><br>You mean JEP-0011? Jeez... they really need to get with the times.
<br><br>> Before i go trying to submit large patch for changes I think might be<br>> necessary, is there any suggestions on how his feature can be<br>> implemented. Is there a good document on how hooks are done? Could I use
<br>> them so plugins can optionally register information for iq:browse or<br>> iq:agents?<br><br>I'm really rusty on the browsing/agents stuff and don't really remember<br>how they work... but I wonder if they could be implemented in terms of
<br>the existing disco support, without requiring any additional<br>configuration. I think "Jabber Browsing" uses a similar scheme to the<br>"identity" element from disco.<br><br>I don't know what spec iq:agents belongs to. That one must have passed
<br>me by. Do you have a reference?<br><br>> (ps, is it the lists fault or gmail that it doesn't want to reply to the<br>> list by default sorry mart).<br><br>The list is configured to not munge the Reply-to header, so you have to
<br>either remember to change the address or use the "Reply to all" command<br>instead of just "Reply". (and then trim out all of the addresses except<br>the list, naturally.)<br><br><br></blockquote></div>
<br>