Programming Jabber

Retrieving vCard information

As well as registering with a JUD, it’s possible that a user has maintained more information about himself—in his vCard. Depending on the Jabber client used, various user information can be stored in a personal vCard, which is stored on the server side. In Figure 10-5, we see the JIM client’s vCard maintenance window, titled User Profile.

The result of entering information and clicking the OK button in Figure 10-5 can be seen in Example 10-4, where an IQ-set in the vcard-temp namespace is made to store the information (some of the vCard tags have been omitted to keep the example short). Notice how no to attribute is specified in the IQ-set and how the result appears to come from the sender ([e-mail]/study). The storage of personal—user-specific—vCard information is a function of the Jabber Session Manager (JSM), which is where the <iq/> element will be routed automatically, as it is coming in over a client connection (defined by the jabber:client stream-level namespace). This is further discussed in Section 5.4.3.1.

Figure 10-5. Updating personal vCard information with JIM

Example 10-4. Setting vCard information in the vcard-temp namespace

SEND: <iq type="set"> <VCARD version="3.0" xmlns="vcard-temp"> <N> <GIVEN>DJ</GIVEN> <FAMILY>Adams</FAMILY> <MIDDLE/> </N> <NICKNAME>qmacro</NICKNAME> <EMAIL> <INTERNET/> <PREF/> [e-mail] </EMAIL> ...