Can you change this to always provide an ETag for consistency with real blobstores? Currently we return the ETag if the `putBlob` request included Content-MD5 or generate it if the filesystem does not support `UserDefinedFileAttributeView` (Mac OS X, NFS mounts). We can either remove the property and unconditionally provide ETag or keep the property and use it on the non-`UserDefinedFileAttributeView` code path.
--- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/850#issuecomment-133155764
