Re: [IndexedDB] Explicitly stablishing the timing of clone creation from Jonas Sicking on 2010-08-15 (public-webapps@w3.org from July to September 2010)

From: Jonas Sicking <jonas@sicking.cc>
Date: Sun, 15 Aug 2010 19:11:00 -0400
To: Pablo Castro <Pablo.Castro@microsoft.com>
Cc: public-webapps WG <public-webapps@w3.org>
Message-ID: <AANLkTim1rs6pcE4Z7Z5ZdPU8Fk0taKwM2uKuPysXGBMo@mail.gmail.com>

On Fri, Aug 13, 2010 at 1:43 PM, Pablo Castro
<Pablo.Castro@microsoft.com> wrote:
> The spec for the asynchronous "put" and "add" methods in object store as well as "update" in cursors don't explicitly state when clones are created, and can even be read as if clones should be created after the function call returned, when the queued up task is executed. This leads to problems where the clone may be modified after the call to put/add/update happens. Wouldn't it be more reasonable to require implementations to always create a clone of the object before returning (i.e. synchronously) and perform the rest of the operation asynchronously?

Yes.

> If we agree on this I'll file a bug and later follow up with some text for the spec.

Please do.

/ Jonas

Received on Sunday, 15 August 2010 23:11:54 UTC