> > >> storage system, as I have read it, just stores a JSON-like object for >> retrieval. The only problem becomes requesting the browser for > > > I think you are bit behind the times ... it used to be so, but look at links > I sent in my previous message (this elephant > http://robnyman.github.com/html5demos/indexeddb/ is not a JSON string, and > yet it resides in the IndexedDB database; look at the URL of the image).
The URL of the image is "elephants.png", which is hardly conclusive evidence. :) Possibly because the page throws an error in Chrome when it attempts to load the image into the IndexDB.
And my point still stands that it is storing a JSON-like object. Not pure JSON, but what you have is an object store and not a relational store. That allows particular elements of the object to be something other than a string. I wasn't trying to be technical about the nature of JSON vs the objects that IndexDB holds but rather point out that it is very flexible in ways that are often easier to conceive of than a SQL relational database.
>> additional storage when you reach the 5MB or 25MB limit or wherever it >> is set. > > > Those are limits on storing data IN the IndexedDB, not Files and Blobs.
Good to know. So there is no limit on putting a blob into the IndexDB? That could lead to some very powerful offline apps. But I can't imagine browser writers wouldn't limit the size of data stored somehow. They wouldn't just allow you to keep creating data upon data in stores until you fill a hard drive... at least I would hope not.
> Firefox for Android and B2G do. I would think that Chrome for Android should > do as well (but not sure, I don't use it).
That's good, but for the other 99.5% of us who use Mobile Safari or the built-in Android browser when we're on a mobile device, how do we stack up? I ask in earnestness because I haven't tackled mobile web development beyond a single failed foray in 2007.
Well, to each their own. I have found all of the base libraries (except Ext which I use continuously at work) to be excellent. Oftentimes they have terrible plugins or addons. And I never liked prototype inheritance _instead of_ traditional inheritance. I like to combine them the way that frameworks allow me to mix and match as I see fit. I often will use a combination of raw language features, jQuery's simplification of DOM traversal, and a full library's inheritance and base widget libraries. But there's no accounting for personal preference or ease of use.