>There is a huge amount of logic about deciding what to cache with quite a
lot of tunable parameters. In addition most serious users develop their own
plugins to control caching logic (all the clients I have worked for have
done so). You could start with looking through the documentation for
cache.
On 8/21/12 5:31 PM, Alan M. Carroll wrote:
Tuesday, August 21, 2012, 2:43:06 PM, you wrote:
In practice, because ATS does not by default cache "cgi looking" URLs very few
video files will be cached. Certainly nothing from YouTube, for instance, unless you
write a customized plugin to do so (y
Wednesday, August 22, 2012, 9:31:55 AM, you wrote:
>> In practice, because ATS does not by default cache "cgi looking" URLs very
>> few video files will be cached. Certainly nothing from YouTube, for
>> instance, unless you write a customized plugin to do so (you might search
> Are you sure? T
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 d
> 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.
The purpose o
