Comments on: HTML5 Client-side Local Storage

By: Nathan Campos

Nathan Campos — Fri, 26 Aug 2011 17:16:00 +0000

Thanks very much. Great article indeed.

Another good reading material: http://developer.apple.com/library/safari/#documentation/iphone/conceptual/safarijsdatabaseguide/Name-ValueStorage/Name-ValueStorage.html

By: Niux

Niux — Mon, 18 Apr 2011 15:00:00 +0000

thank´s, useful information

By: Daniel Fischer

Daniel Fischer — Tue, 14 Dec 2010 15:56:19 +0000

That whole block of code there looks awfully familiar if you read the webkit blog on local database storage from 2007

By: New Twitter Web Client

New Twitter Web Client — Sun, 28 Feb 2010 10:55:23 +0000

[...] use HTML5 and if they do, it would be first mainstream implementation, and we can get GeoLocation, local storage, and what not. The upcoming Twitter Ads are said to be built around Twitter search, so [...]

By: Seif Sallam

Seif Sallam — Mon, 11 Jan 2010 12:58:16 +0000

we should see CouchDB rising soon, as its RESTful API, JavaScript can access it easily.

this can be done in 2 ways:
1. CouchDB integrated in the browser, which can use the replication feature between the Browser and the Database Server, and JS can access it locally
2. Remote access and Local Storage, and in this can it will pull data from CouchDB and store it locally.

By: Taranfx

Taranfx — Sun, 10 Jan 2010 14:25:44 +0000

Yeah, this makes more sense after months of frustration of App Store approval fights

By: Josh

Josh — Sun, 10 Jan 2010 14:02:00 +0000

I just saw an iPhone app the other day that is completely web-based using HTML5 for this kind of stuff. Instead of dealing with the app store approval process they challenged themselves to write an app that was equal to something they could do in a native iPhone app, but in HTML5. It turned out really nice. And the best part? They control it. Then send updates when they want without going through apple approval. And it's completely cross-platform.

By: florin

florin — Sun, 10 Jan 2010 00:47:12 +0000

I guess you need to be consistent in your variable naming:

var db = …
database.execute…