Programming Jabber

Working out who gets what newsfeeds

Definitions of the RSS sources are held within the newsagent itself, but there’s no reference to who might want to receive new items from which sources. We need a way for the component to accept requests, from users, that say things like:

“I’d like to have pointers to new items from Slashdot sent to me, please.”

or:

“I’d also like pointers to new items on Jon Udell’s site, please.”

or even:

“Whoa, information overflow! Stop all my feeds!”

There’s a common theme that binds together components such as the Jabber User Directory (JUD), and the transports to other IM systems such as Yahoo! and ICQ. This theme is known as registration. We’ve seen this before in the form of user registration, described in Section 6.5.2. This is the process of creating a new account with the JSM. Registration with a service such as the JUD or an IM transport, however, follows a similar process, and both types of registration have one thing in common: the jabber:iq:register namespace.

The jabber:iq:register namespace is used to qualify the exchange of information during a registration process. The registration process to create a new user account with the JSM uses the jabber:iq:register namespace to qualify registration data exchanged. The registration process with the JSM to modify the account details (name, email address, and so on) also uses jabber:iq:register to qualify the account amendment data exchanged. Both types of registration requests are addressed ...