HTML5 local storage seems to present some security issues. At least raise some serious ethical questions about how to use it and what for.
I think basically users will eventually get .. (censored) unless one build a specific control interface to give that power back to users. http://dev.w3.org/html5/webstorage/ For Rodéo apps, if each user shares a space on a common shared server, than all the local datas of user X are accessible to all different rodeo apps, So far I understood. Not reassuring! Though, it's not clear to me if the key is the domain name or the actual server : if I open a site with domainNameY.com and the site is actually hosted on host.com, what will be the local storage named? What I understood is : host.com will be the "primary" key for all local storage. And using sub folders will not allow to restrict the scope. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/WWDC-Keynote-HTML5-wide-open-for-On-Rev-revServer-tp2246637p2247681.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
