[Bug 21300] lack of clarity around appendStream

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

--- Comment #2 from Jon Piesing (OIPF) <oipfjon@gmail.com> ---
(In reply to comment #1)
<snip>
> Practically though, the expectation is that the primary use case for this
> method is with a Stream object created by XMLHttpRequest. The details on how
> XMLHttpRequest's Stream object behave are outside the scope of the MSE.

I agree that formally they're outside the scope of MSE however if MSE is making
assumptions about this behaviour then those assumptions should be documented
*somewhere* otherwise you will get implementations of XMLHttpRequest's stream
object that are fine as far as the XHR spec is concerned but fail in strange
subtle ways with MSE. 

Also in most organisations, non-documented assumptions can't have tests written
for them which results in inter-operability issues once there is more than one
implementation.

> If I
> were to speculate though, I'd assume that if the network buffers for the
> request were full, then it would simply stop reading from the socket until
> the Source Buffer consumed enough of the data from the Stream to free up
> space. When more space was available then the UA would start reading from
> the socket again.

In your view, would this allow use-cases where the data from the stream that
has been copied into the Source Buffer starts being copied to the Decoder
Buffer before the last data from the stream has been read in?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 17 March 2013 10:33:43 UTC