Programming Jabber

The jabber:iq:conference namespace at work

Here we see a typical sequence of IQ elements that ensue in the entry negotiations for the jdev room hosted by the Conferencing service on jabber.org’s Jabber server. Information on the jdev room is requested:

SEND: <iq type="get" id="c2" to="[e-mail]">
        <query xmlns="jabber:iq:conference"/>
      </iq>

Note

The JID to which the IQ-get was sent—[e-mail]—works in a similar way to the LDAP reflector earlier in Section 6.2.5.1. There’s no real distinction between conferencing service usernames in the same way that there’s a distinction in the JSM service, but that part of the JID is used to identify each room hosted by that service. In other words, jdev isn’t a “real” user in the JSM sense.

The conferencing service replies with the relevant information:

RECV: <iq type='result' id='c2' to='[e-mail]/hailsham'
                                from='[e-mail]'>
        <query xmlns='jabber:iq:conference'>
          <name>Development Room</name>
          <nick/>
        </query>
      </iq>

We see that the “friendly” name of the jdev room is “Development Room” and that we need to specify a nickname in order to gain entry. There are no other requirements (such as a secret password) that would have been identified inside an extra <secret/> tag in the results.

We choose a nickname, and send this back in an IQ-set. However, before doing this, we must send our presence to the room to invoke the Availability Tracker, which is described in Section 5.4.2.4 in Chapter ...