-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 4/23/09 12:30 PM, Matthew Wild wrote: > On Thu, Apr 23, 2009 at 7:13 PM, Peter Saint-Andre <[email protected]> wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I just chatted with Jonas Lindberg via IM about the requirement in >> XEP-0237 that the value of the 'ver' attribute is a strictly increasing >> sequence number. Other than the similarity to IMAP CONDSTORE, is there >> any strong reason why this is (or seems to be) a MUST? >> > > I'm in favour of it being opaque. I don't see any reason the client > needs to know the sequence number, and it would help server-side > implementations a lot. At the end of the day it is simply a token to > mark for the server the current revision stored by the client. Failing > to recognise the revision the server can simply send the full roster > anyway.
Yes that seems sensible to me. > We would need to decide what to do where we currently set ver='0' though. Yeah, I was thinking about that too. I suppose it could still be zero or some non-opaque string (bad), or that we could add another attribute (bootstrap="true"?) rather than overload 'ver'. Peter - -- Peter Saint-Andre https://stpeter.im/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAknwtSIACgkQNL8k5A2w/vyOPwCfX74ShygoD0PlifVMJ/PGxM6O wKoAnRDBkJ79ySmTo9JcQU6JrEchj81p =aZm+ -----END PGP SIGNATURE-----
