[whatwg] Gears design goals
robert at ocallahan.org
Fri Jun 29 17:25:32 PDT 2007
On 6/30/07, Aaron Boodman <aa at google.com> wrote:
> On 6/29/07, Robert O'Callahan <robert at ocallahan.org> wrote:
> > On 6/30/07, Aaron Boodman <aa at google.com> wrote:
> > > I think as you tried more and more languages, you'd get more resources
> > > associated with the domain. And so the number of resources that would
> > > need to get revalidated on each view of the app would get larger.
> > I don't think so --- just serve a manifest for each user that lists the
> > resources for that user's language only. Is there a problem with that
> > not seeing?
> Manifest? I thought we were talking about the Mozilla proposal.
I mentioned earlier that to get consistent updates without JARs, we have to
add manifest support. Dave is working on it. I think he's following the
Gears manifest format. Speak up Dave :-)
If you visit http://a.com and it serves you a page linking to:
> And then later you come back and it serves you a page linking to:
> You have to revalidate all three files, right? You don't know whether
> en/1.html depends on base.js.
You mean the other way around?
In this case http://a.com would have to list all resources used by the
application. If en/1.html is no longer listed, it is not used by the
application (i.e. not used by base.js) and will not be revalidated.
"Two men owed money to a certain moneylender. One owed him five hundred
denarii, and the other fifty. Neither of them had the money to pay him back,
so he canceled the debts of both. Now which of them will love him more?"
Simon replied, "I suppose the one who had the bigger debt canceled." "You
have judged correctly," Jesus said. [Luke 7:41-43]
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg