[Standards] UPDATED: XEP-0237 (Roster Versioning)

Leonid Evdokimov leon at darkk.net.ru
Wed May 13 16:20:27 UTC 2009


Jiří Zárevúcký wrote:
> If it is a hash of a complete roster (as Peter has told) then the
> server would have to decode this hash, figure out exactly what version
> that was, create a difference, figure out the version for every
> change, and send every change with the appropriate full roster
> checksum again.

No, there is easier way that still conforms to the XEP:

if hash matches - send nothing,
if hash does not match - send whole roster.

See  Implementation Guidelines[1] for details.

[1] http://xmpp.org/extensions/xep-0237.html#impl


Version string is up to server developer - he may do anything he wants
to. Almost. The developer should conform to following precondition:

if only part of roster is sent (as set of pushes) then every push should
be treated as separate transaction and every push should leave
conforming client in consistent state.

-- 
WBRBW, Leonid Evdokimov

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20090513/5abbe4f9/attachment.sig>


More information about the Standards mailing list