Wednesday, August 22, 2012, 6:24:49 AM, you wrote: > Who currently does the actual work of retrieving the file to be cached and > placing it into the cache?
The ATS core handles all cache data. In fact it's an issue that plugins have very limited access. > valid option to allow the plugin to decide what part of the file should be > cached? I can't see that being viable. What would be the benefit of caching only part of the content received by ATS from the origin server? I understand the benefit of caching part of an object because that is all the origin server sent but dropping part of data available seems a bit odd. > Can also a plugin decide if an entry from the cache should or should not be > used? More exactly: is a plugin capable of combining a number of cache > entries and serving the result as a response? A plugin can prevent a cached object from being served, and can select among alternates of the object. In theory you could combine existing cached objects but it would be quite a challenge. You would need to have a transform plugin that copied over to the original client VC, and generate synthetic requests to trigger that transform. My brain hurts just thinking about it. Someday we should build a real API for plugin access to cache.
