Closed Bug 555316 Opened 14 years ago Closed 14 years ago

Implement IndexedDatabaseRequest::open

Categories

(Core :: DOM: Core & HTML, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: sdwilsh, Assigned: sdwilsh)

Details

I'm going to deviate from the current spec here and return an IDBRequest object from open and not have it on the IndexedDatabaseRequest object.  This is a change I've suggested, and it looks like the chromium guys agree, so we are going to prototype it out that way.
Depends on: 555317
I'm trying to decide on architecture here, and need some input.  Should I add a getIndexedDBForPrincipal on nsIDOMStorageManager, or should I add it to it's own interface?  If I add  it to nsIDOMStorageManager, I have a number of questions:
1) Should getUsage also count usage of indexedDB (bet yes, but this method is also sync which is boo).
2) Should I also use the same database file (and should I rename it?).

Thoughts on this?
I don't think there will be much code to share, but I am not aware of any of your implementation details.  I don't think you should reuse the database file.  The structure will be different because you will have to use more indexing and potentially even more then just a single database file (?) as the goal is to be fast.

I suggest to start writing this from scratch and cover it by different interfaces.  In future DOM storage might get drop or obsoleted completely and will be simpler to do that when it's left separated.

You will have to include usage of the database (that for sure can be obtained synchronously) in a per-domain usage, split to usage by web content and by offline application allowed domains/sub-domains.  Just mxr for nsIDOMStorageManager to see the current places.

The only code that you can copy/inspire by potentially is using a memory database in session-only cookies mode and private browsing mode to disallow tracing.
No longer depends on: 555317
This has changed, and we aren't going to be doing lots of small bugs anymore...
No longer blocks: async-IndexedDB
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.