Thank you Alan for stepping in! >>ATS will only cache full object requests. It never caches range requests.
Is this happening also for large files (video files for example) ? I assume that the cache will fill up quite quickly with this approach, isn't it? What is currently the strategy used for deciding which files get cached and which do not? >>There is a team somewhere working on caching partial objects but I don't know what they current state is. We are currently collecting data from you guys (the ATS developers mainly) about how you envision caching the range requests so we maximize our chances of getting our enhancements accepted back into the mainline project. Best regards, Bogdan Graur On Mon, Aug 20, 2012 at 6:21 PM, Alan M. Carroll < a...@network-geographics.com> wrote: > Monday, August 20, 2012, 10:54:31 AM, you wrote: > > >> - does it cache partial objects (the parts corresponding to the > requested > >> ranges) or the whole requested file? > > ATS will only cache full object requests. It never caches range requests. > If an object has been cached in whole, then subsequent range requests will > be served from that cached object. There is a team somewhere working on > caching partial objects but I don't know what they current state is. If a > range request is received by ATS and the object is not in the cache the > request will simply be forwarded to the origin server and no caching will > occur. > >
