That looks really good, there are lots of complicated issues to get this stuff right. Which header differences between one range fetch and the next invalidate all of the old fragments, when should they just update the response headers. What is the right range/partial object chunk size. (Should be configurable per-request.) How do you handle a range request failure so client is ok with response. How do you deal with a range request of indeterminate size.
One question: Under this scheme can part of an object get purged? -William Bardwell ________________________________________ From: Alan M. Carroll [a...@network-geographics.com] Sent: Friday, April 11, 2014 9:26 PM To: dev@trafficserver.apache.org Subject: Proposed partial object caching design During the summit we developed a new proposed implementation for partial object caching. We think it is better than any of previous proposals and, unlike them, likely to be implemented. You can review (as the last section) on the Wiki - https://cwiki.apache.org/confluence/display/TS/Partial+Object+Caching
