[Standards] Proposed XMPP Extension: Roster Versioning

Peter Saint-Andre stpeter at stpeter.im
Thu Mar 6 18:09:57 UTC 2008

Dave Cridland wrote:
> On Thu Mar  6 17:25:18 2008, Peter Saint-Andre wrote:
>> Dave Cridland wrote:
>> > Then it doesn't get versioning. (BTW, I hate that name - there are no
>> > versions kept. It's not like a client can ask for a previous version,
>> > and nor does a server need to keep any previous versions).
>> I'm not wedded to that name. Feel free to suggest another. Roster diffs?
> No, you don't (really) get diffs, either. It's easy to think that a diff
> is generated between two versions, which isn't really happening.
> (Thankfully - it'd be much harder to implement if it were the case).
> Roster change sequencing, which uses a roster change sequence, and
> associates each change with a roster change sequence value?
> Or roster sequencing, etc, for a shorter term. s/version/roster-seq/
> throughout?

Done in version 0.2, other clarifications added as well:



Peter Saint-Andre

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20080306/3ebc72db/attachment.bin>

More information about the Standards mailing list