Allow the HTTP cache to be disabled or created in any location
Review Request #7293 — Created May 8, 2015 and submitted — Latest diff uploaded
The HTTP cache for the API can now be disabled via the
--disable-cachingcommand line argument. It can also be moved to an
arbitrary location with--cache-location FILEor created in memory
with--in-memory-cache. This behaviour is also available to consumers
of the API via theRBClient. Theallow_caching,cache_location,
andin_memory_cachekey word arguments can be used for this.
Unit tests passed.
Ran the following commands:
rbt status --debug --disable-cacherbt status --debug --in-memory-cacherbt status --debug --cache-location /tmp/cache
The debugging information indicated the correct behaviour was taking
place in each instance.