Just to say meh, "me too". Also, no it's enough for javascript to have only a vaguely superficial idea about the format. Webserver should decide on that anyway. Going without appendBytes is about losing freedom - webmasters are now forced to wait for that each particular feature to ramp up enough traction to have it pushed upstream.
FYI, Pandora uses appendBytes to play mp3s. Best thing about it is when evilcorp implements DRM that way, it's a trivial place to place the tap to get clean stream. The positive face of this is of course RTMFP-style controlled P2P object replication. For example adaptive streaming. Adobe gives me rather embarassing protocol to talk to (RTMP), or just lets me write the stream. Hurray! Forcibly switching to different transcode can be matter of single H264 NAL. All done in HTML5, except the bloody Flash display window itself. But only javascript's idea about this is to strip first 13 bytes from every request except the first. On Sunday, April 22, 2012 2:41:00 PM UTC+2, Hadar wrote: > Hello, > > > > There is a new interesting API that already introduced in Google > > Chrome: > > http://html5-mediasource-api.googlecode.com/svn/trunk/draft-spec/mediasource-draft-spec.html > > > > It gives the application-level javascript an API that can help > > implementing ad insertion, adaptive streaming, video editing and more. > > The developer can actually take an HTML5 video buffer (segment) and > > append it to the playback on Javascript. Do you plan to support this > > API? What API websites' client side developers have/will have to > > achieve similar functionality? > > > > Thanks, > > Hadar Weiss _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
