Comment 2 for bug 1384451

The bottom-line is that we want X-Newest to work as expected under normal conditions (i.e. when there are no failures). The contract is that it should return the newest data across all replicas at a given point in time.

Now, in order to handle failure conditions, we have built a stronger consistency model (by enhancing swift code) which is layered on top of X-Newest which fails the request if any of the replica in unreachable/unavailable so that client can retry later.

I don't think there are performance implications. The code needs to be modified to handle the create and update case differently.