Great. Thanks John!!
On Fri, Aug 8, 2014 at 1:48 PM, John Dickinson wrote:
> You are describing one of the ways that Swift does eventual consistency. In
> the scenario you describe, it is indeed possible to get the older version of
> the object on a read. There is no whole-cluster invalidation
You are describing one of the ways that Swift does eventual consistency. In the
scenario you describe, it is indeed possible to get the older version of the
object on a read. There is no whole-cluster invalidation of an object. Swift's
behavior here gives you high availability of your data even
