Re: [IndexedDB] Avoiding reader/writer starvation

2010-08-16 Thread Jeremy Orlow
On Fri, Aug 13, 2010 at 7:30 PM, Pablo Castro pablo.cas...@microsoft.comwrote: In the context of transactions, readers using READ_ONLY and writers using READ_WRITE may block each other when starting transactions, at least for cases where the underlying implementation uses locking for

Re: [IndexedDB] Avoiding reader/writer starvation

2010-08-16 Thread Jonas Sicking
On Mon, Aug 16, 2010 at 3:06 AM, Jeremy Orlow jor...@chromium.org wrote: On Fri, Aug 13, 2010 at 7:30 PM, Pablo Castro pablo.cas...@microsoft.com wrote: In the context of transactions, readers using READ_ONLY and writers using READ_WRITE may block each other when starting transactions, at

[IndexedDB] Avoiding reader/writer starvation

2010-08-13 Thread Pablo Castro
In the context of transactions, readers using READ_ONLY and writers using READ_WRITE may block each other when starting transactions, at least for cases where the underlying implementation uses locking for isolation. Since we allow multiple readers and they can start while other readers were