W3C home > Mailing lists > Public > public-html-media@w3.org > April 2014

Issue with updating/updateend

From: Aymeric Vitte <vitteaymeric@gmail.com>
Date: Wed, 02 Apr 2014 22:46:43 +0200
Message-ID: <533C7733.2090106@gmail.com>
To: "public-html-media@w3.org" <public-html-media@w3.org>
The usual code is something like:

if (!source.updating) {
if (first_chunk) {
     source.addEventListener('updateend',function() {
         if (append_buffer.length) {

The use case is: chunks of 498 B and bandwidth rate of 1 Mbps, and this 
does not work at all, at least with Chrome, it might be a Chrome issue 
and/or a spec issue.

Because between two 'updateend' events, the 'updating' property can 
become false, therefore you can append a chunk at the wrong place, if 
your remove the first part of the code (or replace it by if 
(first_chunk) {source.append...}) then the buffer chaining can stop if 
for some reasons the chunks are delayed.

With streams the problem will disappear, without streams there is a 
workaround, but as I mentionned in a previous post I don't find this 
behavior normal.



Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
Received on Wednesday, 2 April 2014 20:47:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:48:48 UTC