<br><br><div class="gmail_quote">2009/7/28 Jonas Sicking <span dir="ltr"><jonas@sicking.cc></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br></div>The only concern I see with this is that it permanently forces all<br>
windows from the same domain to run in the same process. As things<br>
stand today, if the user opens two tabs (or windows) and navigates to<br>
the two different pages on <a href="http://www.example.com" target="_blank">www.example.com</a>, then a browser could if it<br>
so wished use separate processes to run those two pages. If we enabled<br>
this API the two pages would have to run in the same process, even if<br>
neither page actually used this new API.<br>
<font color="#888888"><br>
</font></blockquote><div>This is one of the arguments for layering on the AppCache: the app would have to take action, through an attribute in the manifest, at a level where the browser could make the decision whether to join two windows into the same process.<br>
<br>a<br></div></div><br>