Trying to get MUC Working

[Gavin Mogan]

So apparently the MUC plugin works pretty well. I still was unable to get
the external component to work.

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.

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?

(ps, is it the lists fault or gmail that it doesn't want to reply to the
list by default sorry mart).
Thanks,
Gavin

On 4/14/07, Gavin Mogan <halkeye at halkeye.net> wrote:
>
> So apparently the MUC plugin works pretty well. I still was unable to get
> the external component to work.
>
> I have noticed that
>
> On 4/13/07, Martin Atkins <mart at degeneration.co.uk> wrote:
> >
> > Gavin Mogan wrote:
> > > I've tried doing mu-conference external component with:
> > >   <Subdomain muc>
> > >       <Plugin DJabberd::Delivery::Local />
> > >       <Plugin DJabberd::Component::External>
> > >           ListenPort 5290
> > >           Secret     password
> > >       </Plugin>
> > >   </Subdomain>
> > > in my config file
> > >
> > > As well as the DJabberd plugin/component:
> > > <Plugin DJabberd::Component::MUC />
> > > <Plugin DJabberd::Plugin::MUC>
> > >    Subdomain muc
> > > </Plugin>
> > >
> > > Neither seem to show up properly in any jabber client's browse
> > interface..
> > > Even when i try to explicitly say use " muc.domain.com
> > > <http://muc.domain.com> " some clients end up just crashing, others
> > say
> > > the service is unresponsive.
> > >
> > > I can't seem to see any logging from Component::External.. Should
> > there
> > > be any?
> > >
> >
> > The MUC component in djabberd is unfinished and probably doen't work. An
> > external component is almost certainly a better idea right now.
> >
> > In order to get the component to show up in service discovery, you need
> > an additional line to register the component as a service:
> >
> > ChildService muc.yourdomain.com Multi-user Conference Service
> >
> > ::Component::External normally generates a lot of log noise even before
> > anything connects to it; it'll tell you on startup that it's starting up
> > and that it's waiting for the component to connect, and then once the
> > component connects it it'll tell you so. Until the component actually
> > connects, messages to the component can sometimes seem to go into a
> > black hole, although most of the time ::Component::External will respond
> >
> > with a "service unavailable" error.
> >
> > It might be a good idea to remove the ::Delivery::Local plugin from that
> > vhost, as I'm not sure if those two will interact well together;
> > components themselves are handled as a delivery plugin.
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.danga.com/pipermail/djabberd/attachments/20070414/fd5b76f8/attachment.htm