- From: <bugzilla@jessica.w3.org>
- Date: Thu, 10 May 2012 15:21:29 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16998 --- Comment #2 from Aaron Colwell <acolwell@chromium.org> 2012-05-10 15:21:28 UTC --- (In reply to comment #1) > This is a welcome change, since it also means that the data doesn't have to > reside on the ECMAScript heap, where out-of-memory can't be handled gracefully. Agreed. I also figured that this change would allow the UA to regulate the append rate so it can have a little more control over the memory usage. > > Is end inclusive or exclusive? The HTTP Ranges header has start and end > inclusive, which is something I've seen mistakes with in test cases at Opera. > I'd suggest using an unsigned length parameter instead of end, since that's > less prone to mistakes. Good point. I like the idea of using a length parameter instead. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 10 May 2012 15:21:39 UTC