update
Click on the red underlined text to get to the source
...
After sending initial presence, the user MAY update its presence
information for broadcasting at any time during its session ...
... unavailable". (Note:
A user's client SHOULD NOT send a presence update to broadcast
information that changes independently of the user's presence and
...
... </iq>
The server MUST update the roster information in persistent storage,
and also push the change out to all of the user's available resources
that have requested the roster. This "roster push" consists of an IQ
...
... roster item, when updating a roster item the server
MUST update the roster information in persistent storage, and also
initiate a roster push to all of the user's available resources that
have requested the roster.
...
... roster item, when deleting a roster item the server
MUST update the roster information in persistent storage, initiate a
roster push to all of the user's available resources that have
requested the roster (with the 'subscription' attribute set to a
...
... remove the roster item from the
user's roster, the user SHOULD update the roster item with
subscription='remove ...
... roster item from
the contact's roster, the contact should update the roster item with
subscription='remove ...
... group in the user's roster. (If a client attempts to
update, create, or delete a list item with a group ...
... a client attempts to create or update a list with non-unique order
values, the server MUST return to the client a <bad-request/> stanza ...