[Bug 21373] New: Improve Coded Frame Processing and Segment Parser Loop algorithms

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

            Bug ID: 21373
           Summary: Improve Coded Frame Processing and Segment Parser Loop
                    algorithms
    Classification: Unclassified
           Product: HTML WG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Media Source Extensions
          Assignee: adrianba@microsoft.com
          Reporter: cyril.concolato@telecom-paristech.fr
        QA Contact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-media@w3.org

I think the descriptions of the Coded Frame Processing (CFP) and the Segment
Parser Loop (SPL) algorithms should be improved.

The CFP algorithm starts with:
"When complete coded frames have been parsed by the segment parser loop then
the following steps are run:"

While the CFP algorithm is invoke from the SPL algo after the step:
"If the input buffer does not contain a complete media segment header yet, then
jump to the need more data step below."

The CFP assumes that SPL has actually detected coded frame boundaries (not just
the header), which is not obvious from reading the SPL algo only.

To clarify that, I'd suggest moving the first sentence of CFP and including it
in step 6.3 of SPL. I'd suggest also moving and rephrasing the note about
progressive parsing after step 6.3. The result would be as follows:

"3. If the input buffer contains one or more complete coded frames, run the
coded frame processing algorithm.
NOTE: The frequency at which the coded frame processing algorithm is run is
implementation-specific. The coded frame processing algorithm may be called
when the input buffer contains the complete media segment or only some complete
coded frames."

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Friday, 22 March 2013 10:22:58 UTC