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

2011-03-30 Thread Jonas Sicking
On Wed, Mar 30, 2011 at 3:57 PM, Jonas Sicking wrote: > On Sat, Mar 26, 2011 at 1:14 AM, Nikunj Mehta wrote: >> What is the minimum that can be in IDB? I am guessing the following: >> 1. Sorted key-opaque value transactional store >> 2. Lookup of keys by values (or parts thereof) >> #1 is essenti

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

2011-03-30 Thread Jonas Sicking
On Sat, Mar 26, 2011 at 1:14 AM, Nikunj Mehta wrote: > What is the minimum that can be in IDB? I am guessing the following: > 1. Sorted key-opaque value transactional store > 2. Lookup of keys by values (or parts thereof) > #1 is essential. > #2 is unavoidable because you would want to efficiently

clarification on 9.1.3

2011-03-30 Thread Phillips, Addison
In section 9.1.3 of the Widget P&C, the first step of the algorithm to find a file says: Let path be the valid path to the file entry being sought by the user agent. "valid path" is defined by a rather strict grammar — paths that have a double slash aren't matched by the grammar e.g. "path//to/

Re: [FileAPI] Result of calling MultipleReads on FileReader

2011-03-30 Thread Eric Uhrhane
On Mon, Mar 28, 2011 at 5:37 PM, Adrian Bateman wrote: > As we continue to experiment with the File API, I'm trying to understand the > rationale for the Multiple Reads section: > http://dev.w3.org/2006/webapi/FileAPI/#MultipleReads > > The spec says: > >   If multiple read methods are called on t