> requ...@w3.org] On Behalf Of Jonas Sicking
> Sent: Wednesday, May 04, 2011 1:21 PM
> To: Jeremy Orlow
> Cc: Israel Hilerio; public-webapps@w3.org
> Subject: Re: [IndexedDB] deleteObjectStore method and updates to
> IDBDatabase.objectStoreNames on the client
>
> On Wed, May 4,
On Wed, May 4, 2011 at 9:49 AM, Jeremy Orlow wrote:
> On Wed, May 4, 2011 at 9:40 PM, Israel Hilerio
> wrote:
>>
>> The reason I was thinking that deleteObjectStore was async was because it
>> returns an IDBRequest interface and the pattern implies that the onsuccess
>> handler needs to be called
On Wed, May 4, 2011 at 9:40 PM, Israel Hilerio wrote:
> The reason I was thinking that deleteObjectStore was async was because it
> returns an IDBRequest interface and the pattern implies that the onsuccess
> handler needs to be called for me to be sure that the operation happened
> successfully.
The reason I was thinking that deleteObjectStore was async was because it
returns an IDBRequest interface and the pattern implies that the onsuccess
handler needs to be called for me to be sure that the operation happened
successfully.
Regarding the createObjectStore, it returns immediately but
Well, createObjectStore is synchronous, so that one's easy. Everything
happens at once in terms of side effects.
As for delete: why is this asynchronous again? It seems easiest just to
make it sync unless there's some major problem with doing so.
Either way, it seems that the change to objectSt
