Client-side storage… more options than cookies
- halfnote [Update: thanks Paul!]
- sticky notes
… not too exciting, but we could do more exciting stuff if we can tackle the x-browser issues. Technology is different per browser, standard has variants.
- Gears: sync’d db, SQL interface, search over the DB, unlimited storage (at least in the beta)
- WHATWG, fr HTML5: Safari 3.1+, WebKit, at least two MB, bit more code,
- FF2+ IE8, WHATWG Global Storage, when values change events are fired, in FF you get up to 5MB, in IE its XML, in FF its an SQLLite DB (allows potentially browser-desktop app) — pretty clean simple code
- userData HTML Behaviors in IE 5.5+, up to 1MB per domain — simplest code
On meebo, they checked out how many people had which available
- 87% Flash (they checked for v8, but this has been available since Flash Player 6, so ymmv)
- 74% have native storage
- gears in the single digits
Note: 97% have one of those, 96% had cookies enabled!
- Persist.js – normalize API, just key-value gears
Note: global storage has widest adoption, but global storage actually has been taken out of the specification!
[Update: slides from this talk have been posted on slideshare]