On Tue, Aug 16, 2011 at 10:52 AM, Israel Hilerio isra...@microsoft.comwrote:
On Thursday, August 04, 2011 11:02 AM, Jonas Sicking wrote:
[snip]
I'd be open to allowing read transactions which are started after a
write transaction to see the before-write database contents. Would
On Mon, Aug 15, 2011 at 11:23 PM, Shawn Wilsher m...@shawnwilsher.com wrote:
On 8/3/2011 10:33 AM, Jonas Sicking wrote:
IndexedDB does however not allow readers to start once a writing
transaction has started. I thought that that was common behavior even
for MVCC databases. Is that not the
On Thursday, August 04, 2011 11:02 AM, Jonas Sicking wrote:
On Aug 4, 2011 12:28 AM, Joran Greef jo...@ronomon.com wrote:
On 03 Aug 2011, at 7:33 PM, Jonas Sicking wrote:
Note that reads are also blocked if the long-running transaction is a
READ_WRITE transaction.
Is it
On Aug 4, 2011 12:28 AM, Joran Greef jo...@ronomon.com wrote:
On 03 Aug 2011, at 7:33 PM, Jonas Sicking wrote:
Note that reads are also blocked if the long-running transaction is
a READ_WRITE transaction.
Is it acceptable for a writer to block readers? What if one tab is
downloading a
On Tue, Aug 2, 2011 at 5:38 AM, Joran Greef jo...@ronomon.com wrote:
I have been spending time on IDB lately and wanted to give feedback as to the
transaction auto-commit interface:
I am trying to write a wrapper around IDB to match the interface of my
server-side data store, which allows
I have been spending time on IDB lately and wanted to give feedback as to the
transaction auto-commit interface:
I am trying to write a wrapper around IDB to match the interface of my
server-side data store, which allows you to:
1. Request a read or write transaction asynchronously.
2. GET,
On Mon, Jul 25, 2011 at 6:28 AM, Joran Greef jo...@ronomon.com wrote:
Regarding transactions in the IndexedDB specification (3.1.7 Transaction):
Once a transaction no longer can become active, and if the transaction
hasn't been aborted, the implementation must automatically attempt to
