Programming Jabber

Custom Configuration

The configuration for the s2s is similar to that of the c2s; after all, it is about managing connections to other hosts. The configuration namespace is, however, a little odd:

<dialback xmlns="jabber:config:dialback">

Dialback? Well, in order to prevent spoofing on a connecting server’s part, the s2s component implements an identity verification mechanism that is used to check that a connecting server is who it says it is. See Dialback for more details.

Note

As the namespace for the exchange of document streams in a client-to-server connection is jabber:client, so the namespace for the exchange of document streams in a server-to-server connection is jabber:server.

There are three immediate child tags in the configuration wrapper tag:

<legacy/>

This acts as a flag that allows “legacy” Jabber servers to connect (or disallows, if it is absent). A legacy Jabber server is one that has Version 1.0 and, of more relevance, no support for the dialback mechanism. Without the tag, an incoming connection from a Version 1.0 Jabber server that didn’t support dialback would be refused.

<ip/>

While a normal Jabber server listens for client connections on 5222, it listens for connections from other Jabber servers on port 5269. This is specified with the <ip/> tag, which has the same characteristics as the <ip/> tag in the c2s configuration settings (more than one tag allowed, specific IP address optional).

<karma/>

Karma is used in the s2s component to control connection ...