[webkit-dev] IndexedDB API
jorlow at chromium.org
Fri Jan 22 00:06:25 PST 2010
(I had forgotten that many of the sql interfaces are prefixed by SQL. So
IndexedDB's Transaction interface doesn't actually conflict because SQL's is
On Fri, Jan 22, 2010 at 12:04 AM, Jeremy Orlow <jorlow at chromium.org> wrote:
> Hm. Now that I look closer, I think the only actual conflict is in the
> "Database" interface. It still seemed worth the webapps email though.
> On Thu, Jan 21, 2010 at 11:40 PM, Jeremy Orlow <jorlow at chromium.org>wrote:
>> On Thu, Jan 21, 2010 at 11:14 PM, Maciej Stachowiak <mjs at apple.com>wrote:
>>> On Jan 21, 2010, at 9:53 PM, Jeremy Orlow wrote:
>>> > A couple of us at Google are starting to look at implementing the
>>> IndexedDB API  in WebKit. We thought a good first step would be to
>>> create the IDL files. The first thing I noticed is that it and the Web SQL
>>> Database API  have quite a few conflicts in terms of their interface
>>> names. I'm wondering how we can work around this.
>>> It seems like this is something that should be fixed in the IndexedDB
>>> > One idea I had was to just add a prefix to every IndexedDB interface.
>>> Maybe something like IDB? I'd probably go ahead and give all the indexed
>>> database API files a "IDB" prefix just to make it clear which files are
>>> connected to that API. Does this sound good?
>>> Even if you rename the files, having multiple interfaces with the same
>>> interface name will still cause problems. I don't think it will even
>>> compile. We could do some interim thing but we really need to get the spec
>> I meant prefixing both the interfaces and the files with IDB which I
>> believe would solve the problem.
>> That said, I agree the correct solution is fixing one or both of the
>> specs. I'll probably try the prefix solution tomorrow though to see if it'd
>> even work.
>>> > Like I said, we're _just_ getting started. Once we've got the basics
>>> down (like the IDL files) we'll probably be writing up a design doc to get
>>> feedback on an end-to-end design and/or soliciting more advice on
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev