The db file path for chromium and chrome on windows vista look like...
C:\Users\<username>\AppData\Local\Chromium\User Data\Default\Application Cache\Index
C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default\Application Cache
Here's the sql statement to run...
You can run that command using the sqlite3 command line tool available here,
http://www.sqlite.org/download.html. Put whatever origin url you'd to give more storage to in there.
As for why and what we're doing about it...
1) The model chrome uses for limiting local storage usage is just a stop gap for now. We have yet to design or build a quota management system. We have conflicting goals to balance and just haven't done it yet.
- make storage freely available for use by webapps
- never prompt the user for permission to use storage or burden them with having to manage these resources
We're looking to balance those conflicting requirements within the storage related APIs that have been adopted (more or less) within the standards bodies.
2) Chrome Applications get unlimited storage if they request it in their chromeapp manifest file. That should include unlimited appcache storage. Chrome webapp support is available in the dev channel (i think), but unlimited storage does not yet extend to unlimited appcache storage. I'll put together a CL for that very soon.
http://code.google.com/p/chromium/issues/detail?id=49993
3) We're interested in pushing the stds bodies to specify more explicit means for webapps to negotiate with users for rights to do things like use local resources.