W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2013

IndexedDB, Blobs and partial Blobs - Large Files

From: Aymeric Vitte <vitteaymeric@gmail.com>
Date: Mon, 02 Dec 2013 18:26:53 +0100
Message-ID: <529CC2DD.4020608@gmail.com>
To: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
This is related to [1] (Use case) and [2] (Reduced test case)

This is about retrieving a large file with partial data and storing it 
in an incremental way in indexedDB.

Instead of maintaining an incremented Blob, the real use case is 
retrieving the Blob from indexedDB, doing new Blob([Blob, chunk]) and 
storing it again in indexedDB, for each chunk, decreasing performances 
even more.

Of course you could wait for having the complete Blob and store it, but 
that's not something very realistic, if you are streaming a 500 MB file 
and an error occurs most likely you would prefer to resume the download 
rather than restarting from the begining.

This seems not efficient at all, was it never discussed the possibility 
to be able to append data directly in indexedDB?

Regards

Aymeric

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=944918
[2] https://bugzilla.mozilla.org/show_bug.cgi?id=945281

-- 
Peersm : http://www.peersm.com
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
Received on Monday, 2 December 2013 17:27:22 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:20 UTC