Issues with LastModified
Alexey Melnikov <[email protected]> Fri, 10 May 2002 13:45:27 -0600
| Newsgroups | gmane.ietf.sacred |
|---|---|
| Organization | ACI WorldWide / MessagingDirect |
| Message-ID | <[email protected]> |
Hi, I would like to reopen the discussion about LastModified field. Firstly, in draft-ietf-sacred-protocol-bss-01.txt UploadRequest doesn't contain LastModified anymore. I suspect it was removed by mistake from the XML schema. Without LastModified in UploadRequest there are no conditional uploads. Secondly, it wouldn't be uncommon for a machine running a Sacred server also to run a NTP client or similar. Now imagine the following sequence of events: 1). Client A uploads a request and server assigns a LastModified value to it. 2). NTP client running on the same machine adjust current time to be 5 minutes to the past from LastModified in 1). 3). Another upload request happens in these 5 minutes, assigned LastModified will be less than in 1). Thus I suggest you change LastModified to be a sequence counter, incremented every time the credential is modified. Regards, Alexey Melnikov __________________________________________ R & D, ACI Worldwide/MessagingDirect Richmond, Surrey, UK Phone: +44 20 8332 4508 I speak for myself only, not for my employer. __________________________________________