On 6/26/13 10:33 AM, Réjean Bouchard wrote:
I understand your point but there is legal obligation that might require you
to know what's is inside your cache. Let's say some illegal content get
cached but you might not know the full url of that. If you want to purge
that and are only aware of the domain. You may want to purge only the
content from that domain and not the full cache. Let say you have 75000000
images and the TS is caching dynamic resized image generator. There is
valid reason to do it on the fly and you might not be aware of what your
cache currently hold and one of those image is simply illegal. In that case
it's really usefull to be able to search the cache to be sure to delete the
file.
If you want to purge that much, and can do generation IDs by e.g. domains,
you should do that. E.g.
https://github.com/godaddy/ats-plugin-cache-key-genid
This is by far the best solution for massive purges, but puts constraints on
how you partition your cache data (by domain, or by URL prefixes or
something that you can impose a generation ID upon).
If you have a cache of the size I think you are, the regex searches will
take days or even weeks to complete. Probably not what you want :). You can
still do what i suggested, presumably you log all requests, so building a
little DB over all URLs that has hit the cache is not difficult, and you can
manage that in some way (outside of ATS) such that it's optimal for your use
case.
-- leif
