The implication is twofold:
1. If widgets are to use one of these storage mechanisms, then we need
to say what (instead of origin) the storage is scoped by, and how a
widget acquires an instance.
2. As far as security policies are concerned, this suggests that we
are acquiring an additional set of complexity earlier than I had
thought.
--
Thomas Roessler, W3C (mobile) <[email protected]>
On Apr 24, 2009, at 10:37, "Arve Bersvendsen" <[email protected]> wrote:
On Thu, 23 Apr 2009 20:17:07 +0200, Thomas Roessler <[email protected]>
wrote:
Guido Grassel is reminding me that the HTML5 storage API keys off
origin. Thy means another wrinkle or the uri scheme/origin
discussion.
Note that only the instantiations of storage, through the
localStorage and sessionStorage, are using origin. The storage
interface itself does not, so I do not see any immediate
consequences with regards to preferences or any uri scheme discussion.
--
Arve Bersvendsen
Opera Software ASA, http://www.opera.com/
