| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: Ie700aa16d91fba53fc5eb2555829cb74d84b12ad
|
|
|
|
|
| |
Bug: 4486011
Change-Id: I1877ce593d441653f75ab14884aa2d85f52652ad
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the filesystem fails, cache performance degrades. Ongoing
writes should not see any filesystem errors: don't punish the
writer who isn't benefitting from the cache. Ongoing reads may
see IOExceptions while streaming files. In practice this will
only happen if the directory disappears during use, as is the
case when a removable partition is removed.
Change-Id: Ibf4d51998d9beaba9f8c86c449fd5c97ca869cee
http://b/3180373
|
|
|
|
|
|
|
|
|
| |
This requires a backdoor for the cache to read the request headers
at put time. This is implemented by getting the HttpEngine, which
will allow us to eventually share the response header parsing.
Change-Id: I177467244e5af0a3dda07883cd58d641bf75362f
http://b/3180373
|
|
This tests what happens when the filesystem fails while reading or
writing the cached files. I still need to test what happens when
there are failures reading or writing the journal.
Change-Id: I48018514ef5b8cc206efc905b1823eb49589c8e8
http://b/3180373
|