ok, i see. how much code would the other tasks share? can you create an issue with the ideas what else the varnish client might be able to do, so i get an idea? i think keeping the invalidator implementation separate from a configuration tool could make sense, if the other part is more than a small utitliy thing.

or could we use some different namespace? what we have are clients for a caching proxy server. `CachingProxy` maybe?

i can live with the namespace if we find nothing better, but its not very obvious for me. http cache is about the whole thing, not only about the invalidation and our clients that trigger invalidation.