W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2008

[whatwg] Caching offline Web applications

From: Michael Nordman <michaeln@google.com>
Date: Tue, 18 Nov 2008 16:30:25 -0800
Message-ID: <fa2eab050811181630r7ed2db75oa7af1b58c3db185d@mail.gmail.com>
On Mon, Nov 17, 2008 at 8:05 PM, Ian Hickson <ian at hixie.ch> wrote:
>
> Based on this and other offline feedback (no pun intended), I've changed
> the spec to make <iframe>s never inherit the manifest.


Seems workable... of course until app developers actually start trying to
use this system, the real world implications of these sort of design
decisions will remain TBD.


> >> * intercept namespaces [new]
> > >
> > > This isn't supported; the network is always consulted. But if the
> > > network request fails, then a fallback resource is used, though it
> > > cannot be generated on the fly.
> >
> > Why? I had assumed this was a simple omission in the original draft. Can
> > you explain the rationale behind not having this feature? What am i
> > missing?
>
> The rationale for not having any feature is the same -- there was either
> not enough rationale for adding it, or the rationale didn't outweigh the
> cost of adding it at this stage. This is something we can delay until a
> later version. It's more important to get interoperable behavior sooner
> than to get a complete API later.
>
>
Fwi, this piece of functionality may warrant some actual consideration.  I
think this would add very little complexity to the spec and implementations,
but would add a great deal of value. Big bang for little buck.

Many applications that use Gears depend on the intercept ability in some
central fashion. Lets just take an example from Google Docs use of Gears.
There are two intercept entries for urls of the form /Doc? and /View?. Doc
provides an editable interface. View provides a read-only view. The document
id is provided to these pages as a query parameter. Upon loading, these
cached pages examine the query params and retrieve the appropiate document
data from the an SQL database, and populate the DOM accordingly. This is a
fairly common use case from what I've seen.

I think the inclusion of a feature along these lines would greatly help
existing Gears users migrate to this new system.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20081118/389a87d2/attachment.htm>
Received on Tuesday, 18 November 2008 16:30:25 UTC

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