Bug 18922 - Add a parser free, codec agnostic example
Summary: Add a parser free, codec agnostic example
Alias: None
Product: HTML WG
Classification: Unclassified
Component: Media Source Extensions (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Adrian Bateman [MSFT]
QA Contact: HTML WG Bugzilla archive list
Depends on: 18920 18921
  Show dependency treegraph
Reported: 2012-09-19 19:14 UTC by Hadar Weiss
Modified: 2012-10-21 15:52 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Hadar Weiss 2012-09-19 19:14:32 UTC
The example in the spec relies on the existence of a "parser" that returns buffers that are full valid segments. Most of the code is not included.

A much more simple example (with all the code included) will help developers to better understand the API and use it.
Comment 1 Aaron Colwell (c) 2012-09-19 19:41:53 UTC
The expectation is that the web application is responsible for determining where the segment boundaries are. This is highly format & deployment dependent. This can be either done in javascript or with the help of backend servers. There is no generic solution that will work in a format agnostic way. The init/media segment abstractions are the best we can do. Lower level than that requires detailed knowledge of the specific format.
Comment 2 Adrian Bateman [MSFT] 2012-10-21 15:52:07 UTC
We could make the code sample format agnostic by not using a specific media type. However, I don't think this is what you're asking for. I think you're asking for the code for the functions not included but in a format agnostic way. As Aaron says, applications will not be able to ignore the format.

Resolving NEEDSINFO. Please provide the example you're asking for and we can review adding it to the spec or into a separate primer document.