Programming Jabber

Update info request

The mod_version module provides a simple service that, at server startup, queries a central repository of Jabber software version information at update.jabber.org. The <update/> configuration tag:

<update><jabberd:cmdline flag="h">yak</jabberd:cmdline></update>

is used to control this query.

If the <update/> tag is present, the query is sent. If the update tag is not present, the query is not sent.

If you do intend leaving the <update/> tag in, you need to make sure that:

• The hostname specified as the value in the tag is resolvable and reachable as this is your Jabber server address to which the central repository will try to send back information (if there happens to be a newer version of the server software—specifically the JSM component—available).

• Your Jabber server is connected to the Internet to be able to reach update.jabber.org. You also need to be running instances of the Hostname Resolution and Server (to Server) Connections components so that your Jabber server can resolve the update.jabber.org host and send the query out.

The JSM component version releases are fortunately not so frequent that you require an automated mechanism to keep up with what’s new; also you may wish to run an internal Jabber server with no connection to the outside world. So it is not uncommon for this section to be commented out. The JSM will still function without this piece of configuration.

It is worth noting here, however, that Jabber clients also use the central ...