[Bug 18921] append(data) should accept any part of media segment

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18921

Aaron Colwell <acolwell@chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acolwell@chromium.org

--- Comment #3 from Aaron Colwell <acolwell@chromium.org> 2012-09-19 19:50:19 UTC ---
(In reply to comment #2)
> (In reply to comment #1)
> > > This will protect the playback from failing. In some cases, there can
> > > be several "small" appends which are part of previous segment which should all
> > > be discarded, until the append of buffer the contain the start of a segment.
> > > 
> > > Without that, js developers must employ parsers to have the accurate offset of
> > > all segments.
> > 
> > Yep.
> 
> 
> 
> The spec says: "It must be possible to identify segment boundaries and segment
> type (initialization or media) by examining the byte stream alone."
> 
> If there is a way for the browser, even a complicated way to discover the
> boundaries, I think it should be done. It has a major significance on the API
> users.

This doesn't mean that it can identify the boundries at arbitrary points in the
stream. This was only intended to mean that it should be able to identify the
difference between the beginning of an initialization segment and a media
segment without any signalling from JavaScript. It doesn't mean you can append
arbitrary combinations in the middle of other segments. That would make
validating the byte stream EXTREMELY difficult and would likely cause more
developer confusion.

This is an advanced media API and expects the web application to be able to
identify where segment boundaries are. The expectation is that some sort of
manifiest, like DASH or HLS have, will be available to the application so that
it can determine where the segment boundaries are w/o having to implement
format parsing in JavaScript

-- 
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 Wednesday, 19 September 2012 19:50:25 UTC