Do not invalidate renderer caches when NO cache_buster is given #158

strk opened this Issue Feb 26, 2014 · 0 comments


None yet
1 participant

strk commented Feb 26, 2014

I think absence of "cache_buster" parameter will currently invalidate existing caches where cache_buster != 0.

The correct behaviour would be to pick whatever cache is available in those cases.

NOTE: when used in conjunction with Windshaft-CartoDB, the cache_buster is ALWAYS given with MULTILAYER endpoints (unified map api), while it depends on the user for legacy endpoints (inline map, table map).

@strk strk added the performance label Feb 26, 2014

@strk strk added this to the 0.19.1 milestone Feb 26, 2014

@strk strk added the enhancement label Feb 26, 2014

@strk strk closed this in 4084c3f Feb 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment