Programming Jabber

Custom Configuration

In Section 4.2.2, we described the elements in this order: component type, component identification, host filter, connection method, custom configuration. Being XML, the configuration format is flexible enough to allow us to manage the ordering (but not the nesting!) of the configuration directives to suit our own layout purposes. In this instance, we come to the custom configuration—the connection method comes afterward.

The sessions component (i.e., the JSM) offers a lot of facilities, which means that in order to attach an instance of the JSM into our Jabber server we have a lot of configuring to do.

Our configuration wrapper tag for the JSM instance is:

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

The tag name jsm is simply representative of what the configuration pertains to; once loaded, the JSM will look for the configuration by the namespace identifier jabber:config:jsm. Within the wrapper tag, we have different sections that approximately relate to the different services that the JSM is going to provide.

Services and Modules

In Section 4.4.4, the method as to how these JSM services are loaded is described in detail. Generally, each service is represented by a tag that specifies a library to be loaded, and the tag name is what is used to refer to the service, thus giving it a name.

For example, the echo service that is used to test the Jabber server (any message sent to a special echo address servername/echo, which is the server name with a resource of ...