W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2011

[whatwg] Proposal for a MediaSource API that allows sending media data to a HTMLMediaElement

From: Robert O'Callahan <robert@ocallahan.org>
Date: Tue, 12 Jul 2011 12:54:44 +1200
Message-ID: <CAOp6jLaf2JV3cEdkTHNLb7Gcv5ofNF_dS7PsjY1bERdFJN3sFw@mail.gmail.com>
It seems to me that the spec is written assuming only one media element is
consuming the MediaSource. But nothing stops multiple elements consuming the
same URL simultaneously. Maybe instead of going through a URL you should add
API directly to media elements.

bytesAvailable is for flow control? Instead of doing it this way, I would
follow WebSockets and use a bufferedAmount attribute to indicate how much
data is currently buffered up. That makes it easy for authors who don't want
to care about flow control to just append stuff without encountering errors,
while still allowing authors who care about flow control to do it.

Rob
-- 
"If we claim to be without sin, we deceive ourselves and the truth is not in
us. If we confess our sins, he is faithful and just and will forgive us our
sins and purify us from all unrighteousness. If we claim we have not sinned,
we make him out to be a liar and his word is not in us." [1 John 1:8-10]
Received on Monday, 11 July 2011 17:54:44 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:34 UTC