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-caching
command line argument. It can also be moved to an
arbitrary location with--cache-location FILE
or 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_cache
key word arguments can be used for this.
Unit tests passed.
Ran the following commands:
rbt status --debug --disable-cache
rbt status --debug --in-memory-cache
rbt status --debug --cache-location /tmp/cache
The debugging information indicated the correct behaviour was taking
place in each instance.
Diff Revision 2
This is not the most recent revision of the diff. The latest diff is revision 4. See what's changed.
orig
1
2
3
4
rbtools/api/cache.py |
---|
rbtools/api/request.py |
---|
rbtools/api/transport/__init__.py |
---|
rbtools/api/transport/sync.py |
---|
rbtools/commands/__init__.py |
---|
rbtools/commands/clearcache.py |
---|