Programming Jabber

Still no connection

After registering a new user, note that there’s still no session. Only after successful authorization (see later in this chapter) is a session created. Although used in authentication (and so implicitly in session creation), the value of the id attribute in the XML stream header returned by the server (which has the value 3B2DB1A7 in Example 7-1) is a connection ID, not a session ID.

So, what can we do at this stage? Well, one of two things: register another user (yes!) or proceed to the authentication stage. Basically, reaching the end of the registration process, we’re back where we started; a “raw” connection where only one of two sequences is valid: the jabber:iq:register or jabber:iq:auth sequence.