OK for the different records but just to understand correctly, when you
fetch {chunk1, chunk2, etc} or [chunk1, chunk2, etc], does it do
something else than just keeping references to the chunks and storing
them again with (new?) references if you didn't do anything with the chunks?
Regards
On Wed, Dec 4, 2013 at 2:13 AM, Aymeric Vitte vitteayme...@gmail.comwrote:
OK for the different records but just to understand correctly, when you
fetch {chunk1, chunk2, etc} or [chunk1, chunk2, etc], does it do something
else than just keeping references to the chunks and storing them again
I am aware of [1], and really waiting for this to be available.
So you are suggesting something like {id:file_id, chunk1:chunk1,
chunk2:chunk2, etc}?
Related to [1] I have tried a workaround (not for fun, because I
needed to test at least with two different browsers): store the chunks
as
On Tue, Dec 3, 2013 at 4:07 AM, Aymeric Vitte vitteayme...@gmail.comwrote:
I am aware of [1], and really waiting for this to be available.
So you are suggesting something like {id:file_id, chunk1:chunk1,
chunk2:chunk2, etc}?
No, because you'd still have to fetch, modify, and re-insert the
On Tue, Dec 3, 2013 at 11:55 AM, Joshua Bell jsb...@google.com wrote:
On Tue, Dec 3, 2013 at 4:07 AM, Aymeric Vitte vitteayme...@gmail.com
wrote:
I am aware of [1], and really waiting for this to be available.
So you are suggesting something like {id:file_id, chunk1:chunk1,
chunk2:chunk2,
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,
On Mon, Dec 2, 2013 at 9:26 AM, Aymeric Vitte vitteayme...@gmail.comwrote:
This is about retrieving a large file with partial data and storing it in
an incremental way in indexedDB.
...
This seems not efficient at all, was it never discussed the possibility to
be able to append data
