correction
This commit is contained in:
parent
b5eb02bf77
commit
42655caacc
1 changed files with 5 additions and 1 deletions
|
@ -11,7 +11,11 @@ problems with S3 remotes, including file size limits, and a memory leak in
|
||||||
the underlying S3 library.
|
the underlying S3 library.
|
||||||
|
|
||||||
The S3 conversion included caching of the S3 connection when
|
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
|
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
|
the API, but got into some type checker messes when using generic enough
|
||||||
data types to support everything. Should probably switch to `ResourceT`.
|
data types to support everything. Should probably switch to `ResourceT`.
|
||||||
|
|
Loading…
Reference in a new issue