so after scanning this thread and the ticket again - it is still unclear
that there could be a completely universal solution.
While it would be nice if the storage API had a checksum(name) or md5(name)
method - not all custom storage backends are going to support a single
checksum standard. S3
This issue just got me again tonight, so I'll try to push once more on this
issue. It seems right now most people don't care that this is broken, which
is a bummer, but in which case I'll just continue using my working solution.
Dan
On Sat, Oct 6, 2012 at 10:48 AM, Dan Loewenherz wrote:
> Hey J