WhatwgStorage Whiteboard

Neil to impl core storage system, jst to impl security/access/scoping. vlad to advise, shaver to cheerlead.

• Can we track "browser context" well enough?
  • https://bugzilla.mozilla.org/show_bug.cgi?id=117222#c125
• UI requirements?
  • need a storage limit (by domain and subdomain) -- global limit for A2
  • expiration policy? (after A2)
• domain hierarchy stuff? (see m.d.platform posting)

• What subset?
  • no DOM object or JS object auto-serialization
  • jst to propose the removal of key enumeration to whatwg list (security reasons)

• sessionStorage using in-memory hash or just another table?
  • vlad: no on-disk storage for security reasons?
  • shaver: what about session saver? (what does it do for session cookies?)
  • spec suggests persistence of session data in this case: 4.9.3
  • darin: cookies have the notion of session only, which is not persisted. the web cache has the concept of "no-store". this storage system needs something like that too. web apps should be given a way to restrict storage to in-memory only.
• globalStorage using mozStorage, simple table
  • look at what history guys did for fast domain-based lookup?