“Real” Virtual Jabber Servers
While looking at Section 4.4.2 earlier in this chapter, we saw how to use multiple <host/>
tags to allow connection to the Jabber server under multiple hostnames.
Although this simple feature might be useful in some circumstances,
a better distinction of Session Management functionality
might be more appropriate.
Taking our a-domain.com and
b-domain.com hostname examples again, we might want
to offer different welcome messages to new users and limit
the authentication possibilities for the b-domain.com
host to zero knowledge only. We also may wish to disable the message
filtering service for the a-domain.com host.
Furthermore, we might want to
offer—in the <browse/>
list—a different set of services for each of the hosts.
Let’s have a look how this can be done. Using the
<jabberd:include/>
tag to organize our configuration XML by component instance definitions, we
might have a jabber.xml configuration file that
looks like Example 4-25.
<jabber> <!-- Common components --> <jabberd:include>./config/common/xdb.xml</jabberd:include> <jabberd:include>./config/common/c2s.xml</jabberd:include> <jabberd:include>./config/common/elogger.xml</jabberd:include> <jabberd:include>./config/common/rlogger.xml</jabberd:include> <jabberd:include>./config/common/dnsrv.xml</jabberd:include> <jabberd:include>./config/common/s2s.xml</jabberd:include> <!-- a-domain.com --> <jabberd:include>./config/a-domain/sessions.xml</jabberd:include> ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access