Alexander Gnauck wrote:
> Dave Cridland wrote:
> 
>> I also have a fondness for modified strictly increasing timestamps,
>> but implementors need to appreciate that computer clocks go backwards,
>> so they need to remember to handle odd cases like that by "letting
>> time catch up" - just using a few ms later than the last timestamp
>> until the real time is greater than the last timestamp.
> 
> for this reason I would prefer a versioning of the roster, so I client
> can just tell the server I have version 235241 of the roster, let me
> know if this is the current roster or send me the changes otherwise.

That seems best to me, too. Heck, the server could store the roster in
SVN for easier diffs between versions. ;-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to