I'm using the S3 API, and I've noticed that every time I call blobStore.putBlob(), the S3 provider requests the bucket's ACL first. From looking at the code, it appears that the ACLs should be cached after the first GET, but I'm not seeing that. With debug logging enabled, I can clearly see the GET https://myDomain/myBucket?acl call happening every time I call putBlob().
Is that expected, or is there something going wrong? And if it's to be expected, is there any way to make jclouds *skip* the ACL check, and just assume it has write access, throwing an exception if that's not the case? The reason I ask is that latency between my client and the Ceph server is really high right now, so I'd like to reduce the calls the server to just 1. (The plan is to co-locate the client and server in the same data center, but I'd still like to reduce round trips to the server as much as possible.) I'm using jclouds 1.6.3. *Steve Kingsland* Senior Software Engineer *Opower * <http://www.opower.com/> * We’re hiring! See jobs here <http://www.opower.com/careers> *
