summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-08-02 19:16:35 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-08-02 19:16:35 -0400
commit4ac62e1c563c3cfd3c3d23046a8c9180e4774d90 (patch)
treef29951a966664ca3a333e06cf3563502e9773fbf /doc
parente2fad935dd469077e58ac4e24b7e2669cba90c6a (diff)
correction
Diffstat (limited to 'doc')
-rw-r--r--doc/devblog/day_209__mass_conversion.mdwn6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/devblog/day_209__mass_conversion.mdwn b/doc/devblog/day_209__mass_conversion.mdwn
index 6278b191a..23de65b2a 100644
--- a/doc/devblog/day_209__mass_conversion.mdwn
+++ b/doc/devblog/day_209__mass_conversion.mdwn
@@ -11,7 +11,11 @@ problems with S3 remotes, including file size limits, and a memory leak in
the underlying S3 library.
The S3 conversion included caching of the S3 connection when
-storing/retrieving chunks. But the API doesn't yet support caching
+storing/retrieving chunks. [Update: Actually, it turns out it didn't;
+the hS3 library doesn't support persistent connections. Another reason I
+need to switch to a better S3 library!]
+
+But the API doesn't yet support caching
when removing or checking if chunks are present. I should probably expand
the API, but got into some type checker messes when using generic enough
data types to support everything. Should probably switch to `ResourceT`.