Name
id — Optional
Synopsis
<iq type='get' id='roster1'/>
If we’re going to rank the elements in terms of the importance
of their being tracked,
<iq/> would arguably come out
on top, as it inherently describes a request/response mechanism. So this
element also has an id attribute
for tracking purposes.
Don’t forget that the pair of XML streams that represent the two-way
traffic between Jabber client and server are independent, and any
related packets such as a request (traveling in one XML stream) and
the corresponding response (traveling in the other) are asynchronous.
So a tracking mechanism like the id
attribute is essential to be able to match packets up.
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.
