- From: <bugzilla@jessica.w3.org>
- Date: Mon, 18 Jun 2012 18:15:53 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16998 --- Comment #6 from Aaron Colwell <acolwell@chromium.org> 2012-06-18 18:15:52 UTC --- (In reply to comment #5) > I am ok with the suggetion of length instead of end, > but I think it is more complex for compute start-end range using (start,length) > model. > In (start,end) model, I only need to make sure the next start will not > overlap with previous end, but in (start,length) model, we need 1 extra step, > to compute the end of previous end using start+length-1, then make sure the > current start does not overlap with it. I'm not sure I completely follow your concern. I agree that the UA must do the extra computation end = start + length - 1, but I think this is relatively minor compared to people incorrectly computing end on their own. In most of the work demo I've done with the Media Source API, I've usually had a starting offset and a length and then had to convert it into a proper Range header. Like many others, I did this incorrectly the first time I tried it. I think using length will prevent many others from making the same mistake. -- 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 Monday, 18 June 2012 18:15:55 UTC