Could you explain the background for this? Where previously jclouds could do work for you (and work that it should seemingly be able to do, i.e. calculate the MD5 for content you've already given it), we now expect you to do the work yourself, and get the implementation right?
Is there any reason the user has to be able to set the MD5 value explicitly? I would think naively that I'd rather kick out the ability to _explicitly set_ the content MD5, and **only** allow you to ask jclouds to calculate it? Also, if we ultimately do want this to go head, then also remove `Payloads.calculateMD5(payload)`, or do we still need that? Failures look real, by the way. Something in the clojure binding: ``` ERROR in (large-container-list-test) (Reflector.java:289) Uncaught exception, not in assertion. expected: nil actual: java.lang.IllegalArgumentException: No matching field found: calculateMD5 for class org.jclouds.blobstore.domain.internal.BlobBuilderImpl$PayloadBlobBuilderImpl ``` --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/218#issuecomment-29695167
