So apparently the MUC plugin works pretty well. I still was unable to get the external component to work.<br><br>I have noticed that with the 4 or 5 main windows clients, half support the disco service discovery properly (i have a MUC patch to make things work better), the other half uses the depreciated iq:browse and iq:agents.
<br><br>Before i go trying to submit large patch for changes I think might be necessary, is there any suggestions on how his feature can be implemented. Is there a good document on how hooks are done? Could I use them so plugins can optionally register information for iq:browse or iq:agents?
<br><br>(ps, is it the lists fault or gmail that it doesn't want to reply to the list by default sorry mart).<br>Thanks,<br>Gavin<br><br><div><span class="gmail_quote">On 4/14/07, <b class="gmail_sendername">Gavin Mogan
</b> <<a href="mailto:halkeye@halkeye.net">halkeye@halkeye.net</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;">So apparently the MUC plugin works pretty well. I still was unable to get the external component to work.
<br><br>I have noticed that<div><span class="e" id="q_111f3a7d4c28dc51_1"><br><br><div><span class="gmail_quote">On 4/13/07, <b class="gmail_sendername">Martin Atkins
</b> <<a href="mailto:mart@degeneration.co.uk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">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>> I've tried doing mu-conference external component with:<br>> <Subdomain muc><br>> <Plugin DJabberd::Delivery::Local /><br>> <Plugin DJabberd::Component::External>
<br>> ListenPort 5290<br>> Secret password<br>> </Plugin><br>> </Subdomain><br>> in my config file<br>><br>> As well as the DJabberd plugin/component:<br>> <Plugin DJabberd::Component::MUC />
<br>> <Plugin DJabberd::Plugin::MUC><br>> Subdomain muc<br>> </Plugin><br>><br>> Neither seem to show up properly in any jabber client's browse interface..<br>> Even when i try to explicitly say use "
<a href="http://muc.domain.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">muc.domain.com</a><br>> <<a href="http://muc.domain.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://muc.domain.com</a>> " some clients end up just crashing, others say<br>> the service is unresponsive.<br>>
<br>> I can't seem to see any logging from Component::External.. Should there<br>> be any?<br>><br><br>The MUC component in djabberd is unfinished and probably doen't work. An<br>external component is almost certainly a better idea right now.
<br><br>In order to get the component to show up in service discovery, you need<br>an additional line to register the component as a service:<br><br>ChildService <a href="http://muc.yourdomain.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
muc.yourdomain.com</a> Multi-user Conference Service
<br><br>::Component::External normally generates a lot of log noise even before<br>anything connects to it; it'll tell you on startup that it's starting up<br>and that it's waiting for the component to connect, and then once the
<br>component connects it it'll tell you so. Until the component actually<br>connects, messages to the component can sometimes seem to go into a<br>black hole, although most of the time ::Component::External will respond
<br>with a "service unavailable" error.<br><br>It might be a good idea to remove the ::Delivery::Local plugin from that<br>vhost, as I'm not sure if those two will interact well together;<br>components themselves are handled as a delivery plugin.
<br><br><br></blockquote></div><br>
</span></div></blockquote></div><br>