From 8fbdf456cd56134f89fd61e6ecd388b4357a12ce Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sybren=20A=2E=20St=C3=BCvel?= <sybren@stuvel.eu>
Date: Fri, 18 Mar 2016 16:38:27 +0100
Subject: [PATCH] Change of plans: caching is done with CacheControl.

Requests-Cache ignores HTTP cache control headers, violating the HTTP
protocol.
---
 README.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index bb3792ea..10a3f5a 100644
--- a/README.md
+++ b/README.md
@@ -26,10 +26,11 @@ Communication & File Structure
 
 Caching is performed at different levels:
 
-* Caching of HTTP GET requests is performed by [Requests-Cache](https://readthedocs.org/projects/requests-cache/).
+* Caching of HTTP GET requests is performed by [CacheControl](https://cachecontrol.readthedocs.org/).
   
-    * Cache is stored in `$CACHE/blender_cloud.sqlite`; by using the SQLite backend,
-      we ensure cache persistence across Blender runs.
+    * Cache is stored in `$CACHE/blender_cloud_http/`; by using the file
+      backend, we ensure cache persistence across Blender runs. This
+      does require the `lockfile` package to be installed or bundled.
     * The code should be made cache-aware and use the Requests-Cache `CachedSession` sessions.
       This allows for more granular control over where in the code cache is (not) used.