@snotling List operations still have eventual consistency: > List operations are eventually consistent. This eventual consistency applies > to operations that get a <list> of objects or buckets. For example, if you > upload an object to a bucket, you can immediately download that object and > get its ACLs because object uploads are strongly consistent. However, if you > upload an object to a bucket, and then immediately perform a list objects > operation on the bucket in which the object is stored, the uploaded object > might not immediately appear in the returned list of objects. This is also > true if you create a bucket and then immediately perform a list buckets > operation. The newly-created bucket will be immediately available for use, > but the bucket might not immediately appear in the returned list of buckets.
We mostly use this attribute for tests to clear containers, for which we need to know if list is strongly consistent. jclouds could break the consistency model out into various operations in a more granular way; would you like to look into this? Here is another reference with cross-provider consistency results: https://github.com/andrewgaul/are-we-consistent-yet#observed-consistency --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-google/pull/121#issuecomment-69632353
