- From: <bugzilla@jessica.w3.org>
- Date: Wed, 22 Jun 2011 01:10:32 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12530 --- Comment #8 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2011-06-22 01:10:31 UTC --- It's not clear to me what the difference is between a "buffered" track and a "streaming" track, and why they need to have different interfaces. I don't think "streaming tracks" should have pause() or resume() methods on them as shown in comment #7. pause() implies that when you resume() later you'll carry on from where you left off, but we don't want tracks to get out of sync (I can't think of any use-cases for it, and I don't want to implement it). It does make sense to pause and resume entire streams (except for real-time ones, but we can just skip ahead the entire stream when resuming those), and it makes sense to enable and disable particular tracks, and I think that's what's wanted in comment #7. -- Configure bugmail: http://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 Wednesday, 22 June 2011 01:10:37 UTC