jabber:iq:autoupdate
The Update Info Request configuration description in Section 4.4.3.6 in Chapter 4 describes a mechanism for Jabber servers to query a software version information repository to find out about new versions of the server.[1] This version information repository that responds to queries is also known as the Auto-Update service.
Not only can servers request software update information, clients can too. The procedure is the same in both cases and
involves the jabber:iq:autoupdate and
jabber:x:autoupdate namespaces. If clients
support this software update information request, it will usually be in the form of a “silent” request that it sends out
at startup. The sending out of this request can often be switched
on and off in the client’s configuration.
The conversation starts with the requester sending a special availability packet to the information repository. Currently, there are two such public repositories: one running at jabber.org covering a wide range of Jabber software and the other running at jabber.com covering certain clients including JabberIM. This special availability packet looks like this:
SEND: <presence to='959967024@update.jabber.org/1.6.0.3'/>
This is a directed
<presence/> packet because it has a
to attribute. What’s even more interesting is that if we break down the JID, we’re left with 959967024 as the
username, update.jabber.org as the
hostname, and 1.6.0.3 as the resource. This doesn’t mean that the availability is destined for a user ...
Get Programming Jabber now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
