W3C home > Mailing lists > Public > whatwg@whatwg.org > July 2009

[whatwg] Installed Apps

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 28 Jul 2009 14:56:10 -0700
Message-ID: <63df84f0907281456w5ce3349fj477fa81d45f6367c@mail.gmail.com>
On Tue, Jul 28, 2009 at 2:23 PM, Adam de Boor<adeboor at google.com> wrote:
> 2009/7/28 Jonas Sicking <jonas at sicking.cc>
>> The only concern I see with this is that it permanently forces all
>> windows from the same domain to run in the same process. As things
>> stand today, if the user opens two tabs (or windows) and navigates to
>> the two different pages on www.example.com, then a browser could if it
>> so wished use separate processes to run those two pages. If we enabled
>> this API the two pages would have to run in the same process, even if
>> neither page actually used this new API.
> This is one of the arguments for layering on the AppCache: the app would
> have to take action, through an attribute in the manifest, at a level where
> the browser could make the decision whether to join two windows into the
> same process.

Though I think in most implementations, even by the time you realize
that there even is an AppCache manifest, you've already chosen which
process to use to run the page.

But I agree that it's at least theoretically possible to solve this if
you use an AppCache solution.

/ Jonas
Received on Tuesday, 28 July 2009 14:56:10 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:14 UTC