S3: finish converting to aws library
Implemented the Retriever. Unfortunately, it is a fileRetriever and not a byteRetriever. It should be possible to convert this to a byteRetiever, but I got stuck: The conduit sink needs to process individual chunks, but a byteRetriever needs to pass a single L.ByteString to its callback for processing. I looked into using unsafeInerlaveIO to build up the bytestring lazily, but the sink is already operating under conduit's inversion of control, and does not run directly in IO anyway. On the plus side, no more memory leak..
This commit is contained in:
parent
a6da13c1e9
commit
3659cb9efb
3 changed files with 35 additions and 12 deletions
4
debian/changelog
vendored
4
debian/changelog
vendored
|
@ -16,9 +16,9 @@ git-annex (5.20140718) UNRELEASED; urgency=medium
|
|||
were incompletely repaired before.
|
||||
* Fix cost calculation for non-encrypted remotes.
|
||||
* Display exception message when a transfer fails due to an exception.
|
||||
* WebDAV: Sped up by avoiding making multiple http connections
|
||||
* WebDAV, S3: Sped up by avoiding making multiple http connections
|
||||
when storing a file.
|
||||
* WebDAV: Avoid buffering whole file in memory when uploading and
|
||||
* WebDAV, S3: Avoid buffering whole file in memory when uploading and
|
||||
downloading.
|
||||
* WebDAV: Dropped support for DAV before 1.0.
|
||||
* S3: Switched to using the haskell aws library.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue