- From: Ian Hickson <ian@hixie.ch>
- Date: Thu, 26 Nov 2009 02:34:46 +0000 (UTC)
- To: João Eiras <joaoe@opera.com>
- Cc: public-webapps@w3.org
- Message-ID: <Pine.LNX.4.62.0911260233380.14150@hixie.dreamhostps.com>
On Thu, 26 Nov 2009, João Eiras wrote:
> > >
> > > Would be much more simple to just delete the database explicitly
> >
> > Yes, but is this something that will happen often enough to matter?
>
> Unfortunately, that question has two answers. It should happen often,
> but I doubt web developers will ever bother to clean up the data they
> don't need :)
>
> From my personal experience, it's good to do quick synchronous cleanup
> during testing. An heuristic like "delete database if data file is
> empty" would need to be implemented when the database is no longer in
> use by any webpage, so the dom object is garbage-collected and the
> underlying database deleted.
During testing you can do it manually (why would you do it from code?). I
think in practice we wouldn't see production code deleting databases.
> Still on the same topic, why not also allow database names to be listed
> somewhere ? It fits really nicely the use case of developer tools with
> web UIs. Something like
>
> interface Window {
> readonly DOMStringList databases;//or databaseNames
> }
>
> should be enough IMO.
If the API gains traction, that would be a sensible addition. I don't want
to add features at this point without more adoption, though.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 26 November 2009 02:35:15 UTC