W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2007

[whatwg] Gears design goals

From: Andy Palay <ajpalay@google.com>
Date: Sat, 30 Jun 2007 13:54:57 -0700
Message-ID: <c75952c20706301354w2f4bb1e1v96bcc468a82c2462@mail.gmail.com>
On Jun 29, 2007 5:41 PM, Robert O'Callahan <robert at ocallahan.org> wrote:
> 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?

That layout may not be the optimal layout for everyone (even perhaps Google,
as it was a choice made before considering offline applications and how they
will share information, etc.).  The desire to share data and code could lead
people to put all apps under a sigle domain.

As for the burden to put apps in their own domain -  First it seems to be an
unnecessary requirement. I build an app, I choose a URL as I normally would
and I would hope everthing would work out fine. Second it doesn't work well
for environments where access to the domain is not possible. Consider the
case of internal corporate apps. People post new web apps using their
'individual' internal corporate web server. They can choose whatever name
they want. What they don't have is access to the domain in order to do
this.  I grant that this scenario is currently not well supported by the
Gear's security model (something that I believe will need to change), but it
is a real use of technology.

> 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.

I'm still not sure why not have consistency enforced at the application
level. This way an application can pull code from whereever it needs to
regardless of the directory structure.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20070630/4fe3897d/attachment.htm>
Received on Saturday, 30 June 2007 13:54:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:56 UTC