On 8/6/12 8:04 AM, Ira Heffan wrote:
My company (TopCoder) on behalf of our client (Comcast) would like to make
improvements to the range-handling of the ATS cache, basically addressing this
issue: https://issues.apache.org/jira/browse/TS-974. For example, as we
envision it, after our develop
On Aug 6, 2012, at 11:44 AM, Nick Kew wrote:
> You should also note that any substantial contribution would
> need IP clearance from yourselves and your clients.
> Details at www.apache.org.
That is our plan. Thanks for your help.
Thanks,
Mark Vickers
VP Software Architecture
Comcast
I would like to note that I am actively working on less drastic changes to
range handling, specifically to move the range data from the object header to
the alternate header. That will be needed before the further improvements here
are implemented.
yeah, glad to hear that you guys may take this hard task, and my team
may help on review & guide you on the cache rebuild. as it will be a
tough task, and the redesign of the very low disk layout may introduce
big problem, I'd suggest you post your desgin docs on the cwiki:
https://cwiki.apache.or
On Mon, 6 Aug 2012 10:04:50 -0400
Ira Heffan wrote:
> Thanks for any guidance.
First, please don't post here in a followup to an unrelated message.
You're starting a new topic, so you start a new thread.
Second, do you have or plan a test suite that will demonstrate
the problem you're looking
My company (TopCoder) on behalf of our client (Comcast) would like to make
improvements to the range-handling of the ATS cache, basically addressing this
issue: https://issues.apache.org/jira/browse/TS-974. For example, as we
envision it, after our development effort, the cache will be able to
