> Hi, > > How is creating a separate module and a module in a separate jabberd different? > They both have to communicate via a socket to the 'main' jabberd, right? > Wouldn't the advantage to have multiple threads be nullified?
Only if your clients are forced to connect to only one jabberd. But in my case my clients use gabber to the "main" jabberd and a mutt-hack for the "maildir" jabberd. The only reason I have two Jabber daemons is that if the "maildir" jabberd crashes my clients still have gabber working fine. In those rare cases I would like to route from either jabberd the multi threading is nullified, allthough one might want to keep that option available. For instance, you could have the "maildir" jabberd as the "default" and it will always route IM stuff to the "main" jabberd. Doing the other way around will be innefficient since the purpose of having the "maildir" jabberd instance was to get multi threading capabilities. /P _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
