W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2011

Re: [IndexedDB] Design Flaws: Not Stateless, Not Treating Objects As Opaque

From: Keean Schupke <keean@fry-it.com>
Date: Thu, 31 Mar 2011 08:38:45 +0000
Message-ID: <AANLkTikmE44O5g2Ss-2H7=SN=8=8PC=9PFXaJcwM_9C-@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Joran Greef <joran@ronomon.com>, public-webapps@w3.org
I was the one that asked for callbacks.

> but what do we do if those callbacks don't
> return consistent results? Or even do evil things like modify the
> stores where data is being inserted?

If the callback maps all values to a sort-order of '1' there could only ever
be one entry in the index... its not hard, the callback is passed an
immutable copy of the object and returns a sort-order as a binary-blob. If
you capture the object store in the closure you of course you could do evil
things as side-effects. But that is true in any non-purely-functional
language, you can always do evil things with side-effects.

> In short, I don't think we'll get much further here without a concrete

Which basically means nobody working on the current implementations
understands the issues, or thinks the issues are unimportant?

Received on Thursday, 31 March 2011 08:40:05 UTC

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