LocalStorage: Difference between revisions

[[User:Roc|Roc]] I think that trying to provide structured storage on the client is hopeless for the same reasons that trying to provide structured storage in a filesystem is hopeless. Whatever model we choose will never be the right model for the majority of applications. Furthermore, it diverges from today's Web programming models. I think we should just provide a simple filesystem API --- essentially, a persistent hashmap from string keys to string values --- slightly enhanced cookies. Remember that developers will want to at least do all the things they do with cookies today, including obfuscation, encryption, and on our side, quota management. People can build libraries on top of this if they want to. They can build libraries for indexing, LIFO cache management and so on.

[[User:VladVukicevic|VladVukicevic]] 18:00, 7 Jul 2005 (PDT): That's my thinking as well -- something like "supercookies" instead of fully queryable structured storage.  At the very least, they'd be much simpler to start to use.  We can also provide helpers for serializing a JS Object to/from the value format, which should take care of most consumers' needs.  I wouldn't try to just use the cookies api though, since unlike any local-cookies (brownies?) these would never be transmitted to a remote server as part of a request.  I think a simple hash map would fit well with the AJAX model as well.

[[User:Roc|Roc]] I agree so I deleted that part of my comment.