<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<br><div><div>On Sep 23, 2007, at 5:41 PM, Robert O'Callahan wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On 9/21/07, <b class="gmail_sendername">Ian Hickson</b> <<a href="mailto:ian@hixie.ch">ian@hixie.ch</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Provide methods and/or properties for the following:<br><br> * Add a resource to the cache. The resource persists (it's a<br> permanent addition to the manifest.)</blockquote><div><br>So if an update retrieves a new version of the manifest from the server, what will happen to dynamically added resources? </div></div></blockquote><div><br class="webkit-block-placeholder"></div><div>I think Ian's proposal clarified that dynamically added resources would remain after a manifest update (though of course, you can remove them through script).</div><br><blockquote type="cite"><div><div><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">Nondeterminism about which cache might be used to serve a given URI seems highly undesirable to me. This could easily lead to interoperability problems.</span></div></div></blockquote><div><br class="webkit-block-placeholder"></div><div>I believe the only nondeterminism is for top-level resources that appear in more than one cache. An alternate possibility is to require that they be served from the most recently updated cache. However, the counter-argument might be that operations like "open image in new window" should pass the cache along to the resulting new top-level browsing context. Perhaps it should be required that the newest available offline cache is used, except optionally in such cases. I'm not sure how that could be well-defined however.</div><div><br class="webkit-block-placeholder"></div><div>Regards,</div><div>Maciej</div><div><br class="webkit-block-placeholder"></div></div></body></html>