Ahhh...I just saw your query about jStorage in the JS forum.
I think that is barking up an entirely wrong tree.
What happens if a user logs in at the office, does some work, logs out.
Then he goes home and logs in from home, from a different computer.
Or he wants to check something with his iPad or iPhone.
*ANY* kind of local storage is *USELESS* for this kind of thing, in my never overly humble opinion. I simply can *NOT* get excited about storing anything important to any kind of real-world business situation on the user's local computer.
If you want to store the current progress/state of a user's work and you want it to be associated with his/her *LOGIN* and not just a specific single computer, then you *MUST* store it on the server. Period.
The local storage option might have been okay 10 years ago, when almost nobody had more than one computer or device that they logged in from, but it's an utterly CRAP solution into today's world and will only get to be a worse answer as time goes on.
Heck, even here at home, I occasionally login from my wife's Android pad rather than walk downstairs to my computer. I would be *ENORMOUSLY* annoyed at any system that depended on local storage to remember where I left off.
An optimist sees the glass as half full.
A pessimist sees the glass as half empty.
A realist drinks it no matter how much there is.