1,295
edits
LocalStorage: Difference between revisions
→Storage
| Line 145: | Line 145: | ||
different site, should also be easy to access. (Think of | different site, should also be easy to access. (Think of | ||
mail.yahoo.com and address.yahoo.com.) | mail.yahoo.com and address.yahoo.com.) | ||
: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. In fact, I would suggest that we simply use cookies as the API, but relax some of the limits. | |||
===UI=== | ===UI=== | ||