[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mina-dev
Subject:    Re: [jira] Commented: (VYSPER-172) Allow modules to register for a
From:       Bernd Fondermann <bernd.fondermann () googlemail ! com>
Date:       2009-08-28 10:41:31
Message-ID: 88f6e29a0908280341i14cabc2dg658115d295254e2c () mail ! gmail ! com
[Download RAW message or body]

On Fri, Aug 28, 2009 at 11:23, Niklas Gustavsson (JIRA)<jira@apache.org> wrote:
> 
> [ https://issues.apache.org/jira/browse/VYSPER-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12748761#action_12748761 \
> ] 
> Niklas Gustavsson commented on VYSPER-172:
> ------------------------------------------
> 
> Great, that confirms my understanding of the words and makes it more clear to me \
> what you meant in the original comment. If so, MUC should be able to run as both a \
> in-server component and as an external component and it should be a module since it \
> relies heavily on disco. 
> Could you elaborate a bit on the last part of this sentence: "they both live on \
> their own separate component subdomain and have their own set of stanza handlers - \
> both of what modules can't do. ". Modules seems to be able to to have stanza \
> handlers ...

Yes, but they register with the main server's stanza handler set as
contained in the main ProtocolWorker (extends StanzaProcessor).
Components now can have their completely separate own set of handlers,
see ComponentStanzaProcessor.

> and live on the subdomain?

No, they can't as 'modules' anymore. They can only as 'components'. Or
the other way round: Modules which are not components cannot live on
their own subdomain.

Thanks for asking, this is important stuff to have publicly said. Will
have to go into docs and javadocs at some point...

  Bernd


[prev in list] [next in list] [prev in thread] [next in thread]