I.e. maximum storage size, scope (global, 2nd level domain, any domain), life cycle (when is it cleared), etc.
PersistJS falls back on flash and cookies, which is bad (flash slows down browser during page loading, cookies fatten your network requests). Store.js uses localStorage, globalStorage and IE behaviors which do not have those negative side effects.
"So far tested in
Tested in Firefox 2.0
Tested in Firefox 3.0
Tested in Firefox 3.6
Tested in Chrome 5
Tested in Safari 4
Tested in Safari 5
Tested in IE6
Tested in IE7
Tested in IE8
Tested in Opera 10"
Does it mean it works on IE6+? Does IE6 have local storage?
Been available since IE 5.5, apparently. Who knew?
dHTML+TIME could even use dynamic generated music
But I guess Microsoft is too obsessed with .Net and Silverlight now.
Beyond that you're using curly braces when they're not strictly required, which seems inconsistent. I would expect either both all the time or both only when strictly necessary.
Looks great by the way!
MilkCrate is a wrapper around html localStorage/globalStorage that provides support for saving and querying collections of objects.
MilkCrate attempts to implement a similar querying interface to mongoDB.
So, all hopes for cross-domain user tracking are still doomed. sigh
I am left to experiment with user fingerprinting md5(user-agent, http accept and screen resolution) but that is less than ideal situation.
They use a central domain and window.postMessage to make a secure but shared storage.
I would certainly hope so...
Edit: I misread "is" as "could be". It's a good thing to have because it could be a good thing to use. It may be a bad thing to have enabled by default, but it's a bad thing to omit outright.
I don't have access to IE5.5, would love to have someone test it.
IETester hooking is not perfect yet, but the engine is the correct versioned engine used on each tab. You can find more information here :
Fix issue 1, rename store.del() to store.remove()
18 minutes ago