[whatwg] Gears design goals

On 6/30/07, Andy Palay <ajpalay at google.com> wrote:
> But it does place a very large burdon on the servers. Google would expect
> to have quite a few applications and my guess is the last thing we would
> want is to keep pinging every application to see if it up to date whenever
> any application is used.

My Google apps currently use mail.google.com, docs.google.com,
picasaweb.google.com ... Calendar uses www.google.com, I don't know why :-)
So most of these apps have their own domains, and won't face a problem here.
Is it overly burdensome to put separate apps in their own domains?

If it is, then I would suggest simply allowing consistency to be partitioned
by directory as well. I'm not sure of the best way for the server to
configure that, though.

In fact while we want to make sure the user has the most up to date version
> we don't need to check on every use. In most cases the current captured
> version will be fine. The only time that is not the case is when the old
> version has been made obsolete by a newer version. Unfortunately this can
> occur at anytime, including when the application is running. So in that case
> the server needs to tell the client application that it has to force an
> immediate reload. So the client can always run the currently saved app,
> check for updates at a convenient time (and in reality not too often).


"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...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070630/afacb468/attachment.htm>

Received on Friday, 29 June 2007 17:41:20 UTC