Comment 1 for bug 1384451
Revision history for this message
| clayg (clay-gerrard) wrote Re: x-newest doesnt return newest data under certain race conditions | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I didn't ever really think about using X-newest with containers - that works?
Oh, how interesting, if you do your metadata updates with PUT instead of POST you can get a newer timestamp... hrmm....
Aren't container metadata updates sorta racy anyway? What with read modify write all up in there?
Also you say "[in]consistencies in our system which isn't acceptable" - can you elaborate? AP systems like Swift tend to push clients into gracefully handling stale reads. I'd be fine with minimizing that if the performance implications are reasonable - but what do you expect x-newest to do under failure?