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

Re: Two years on and still no sensible web storage solutions exist

From: Florian Bösch <pyalot@gmail.com>
Date: Mon, 12 Nov 2012 17:17:18 +0100
Message-ID: <CAOK8ODgOMErqJZCdV_X9n5Gc7Qcu7K+TdWo8DOokSfNSx1BTGA@mail.gmail.com>
To: Kyle Huey <me@kylehuey.com>
Cc: Charles McCathie Nevile <chaals@yandex-team.ru>, Andrew Wilson <atwilson@google.com>, Todd Blanchard <toddvblanchard@gmail.com>, Webapps WG <public-webapps@w3.org> 
On Mon, Nov 12, 2012 at 3:49 PM, Kyle Huey <me@kylehuey.com> wrote:

> Er, IndexedDB should handle ArrayBuffers just fine.  If you're seeing
> problems with that that's an implementation bug, not a case that the spec
> failed to handle.
>
You're right it does, I just checked. Nevertheless there are some issues.

This testsite: http://codeflow.org/issues/indexeddb.html
Putting 50mb takes between 2.5 to 8 seconds. Getting it between 2 to 4
seconds.
Putting 100mb doesn't work in Chrome at all and throws an exception on the
put after half a second.

For comparison, in python:
Writing 50mb takes between 40-80ms. Reading takes around 50ms.
Received on Monday, 12 November 2012 16:17:50 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:56 GMT