<br><br><div><span class="gmail_quote">On Jun 26, 2007 4:26 PM, Robert O'Callahan <<a href="mailto:robert@ocallahan.org">robert@ocallahan.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="CSS_CV_QUOTED_TEXT_">On 6/27/07, <b class="gmail_sendername">Aaron Boodman</b> <<a href="mailto:aa@google.com" target="_blank">aa@google.com</a>> wrote:</div><div><div class="CSS_CV_QUOTED_TEXT_"><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;">
Great! So where do we differ on the implementation of those goals? Is<br>there an up-to-date spec I can read?</blockquote></div><div><br><a href="http://www.campd.org/stuff/Offline%20Cache.html" target="_blank"><span style="font-family: monospace;">
</span>http://www.campd.org/stuff/Offline%20Cache.html</a><br><br>Right now I think we're missing just one thing from your list of goals (excluding the vexatious "multiple resources for one URI" goal): a way to get consistent updates without relying on JAR files (and hence changing URIs). As I mentioned earlier, I think we can get that by simply stating (and implementing!) that updates to all offline-cached resources in a domain --- that were requested by pages in the same domain --- occur atomically as a group, similar to what Gears does. That leaves one issue, which is the ability to add new resources as part of such an atomic update; to get that, we probably should add an offline-manifest DOM API or <link> type, which pulls in a JSON manifest and requests all the resources in it.
<br></div><div class="CSS_CV_QUOTED_TEXT_"><br></div></div></blockquote><div>So I don't know why one would want to maintain atomicity at the domain level as opposed to the application level. When I run an application I want to make sure I get the latest version of the application. Not sure why it would mean that I want to make sure that I update all the applications from that domain. This could place an unnecessary load on the servers for no great gain for the user. Am I missing something?
<br><br>Andy<br><br></div></div><br>