mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-22 01:02:17 -05:00
text tweak for consistency with rfc3921bis
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@4042 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
13a7249843
commit
3868eeec71
@ -156,7 +156,7 @@
|
||||
<p class='def'><strong>Definition:</strong> The <strong>'ver' attribute</strong> is a string that identifies a particular version of the roster information. The value MUST be generated only by the server and MUST be treated by the client as opaque. The server can use any appropriate method for generating the version ID, such as a hash of the roster data or a strictly-increasing sequence number.</p>
|
||||
</section2>
|
||||
<section2 topic='Client Request' anchor='request'>
|
||||
<p>If a client supports roster versioning and the server to which it has connected advertises support for roster versioning as described under <link url='#feature'>Stream Feature</link>, then the client MUST include the 'ver' element in its request for the roster. If the server does not advertise support for roster versioning, the client MUST NOT include the 'ver' attribute. If included, the 'ver' attribute is set to the version ID associated with its last cache of the roster.</p>
|
||||
<p>If a client supports roster versioning and the server to which it has connected advertises support for roster versioning as described under <link url='#feature'>Stream Feature</link>, then the client MUST include the 'ver' element in its request for the roster. If the server does not advertise support for roster versioning, the client MUST NOT include the 'ver' attribute. If the client includes the 'ver' attribute in its roster get, it sets the attribute's value to the version ID associated with its last cache of the roster.</p>
|
||||
<example caption="Roster get with version ID"><![CDATA[
|
||||
C: <iq from='romeo@montague.lit/home' id='r1h3vzp7' to='romeo@montague.lit' type='get'>
|
||||
<query xmlns='jabber:iq:roster' ver='ver14'/>
|
||||
|
Loading…
Reference in New Issue
Block a user