<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3395" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left>Michael Nordman<SPAN class=954415617-27082009>
wrote:</SPAN></DIV><FONT color=#0000ff></FONT><FONT color=#0000ff></FONT><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">And
to confound the problem further, UAs dont have meta-data on hand with which to
relate various pieces of local data together and attribute them to a specific
user-identifiable 'application'. Everything is bound to a security-origin, but
that doesn't clearly identify or label an 'application'.</BLOCKQUOTE>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN class=954415617-27082009>Agreed. It
would be nice if data was bound to namespaced contexts on a more fine-grained
model than origin/hostname. This could potentially be done using the path-based
mechanism I just posted about in the thread titled "origin+path namespacing and
security".</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN
class=954415617-27082009></SPAN></FONT> </DIV>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN class=954415617-27082009>It would
be good with a single mechanism that can be extended to confine applications
within their own namespaces (to not interfer with each other), be used for
security, and for assisting user decisions on what to keep or
delete.</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN
class=954415617-27082009></SPAN></FONT> </DIV>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN class=954415617-27082009>Best
regards</SPAN></FONT></DIV>
<DIV dir=ltr><FONT face=Verdana size=2><SPAN
class=954415617-27082009>Mike</SPAN></FONT></DIV></BODY></HTML>