[whatwg] Application deployment

Kristof Zelechovski giecrilj at stegny.2a.pl
Wed Jul 30 01:04:46 PDT 2008

The documents belonging to the container should not be available directly
from the server, except when they are served via a server extension that
goes to the container to get them.  This effect should be easy to achieve on
the server side.




From: whatwg-bounces at lists.whatwg.org
[mailto:whatwg-bounces at lists.whatwg.org] On Behalf Of Robert O'Callahan
Sent: Wednesday, July 30, 2008 6:45 AM
To: Dave Singer
Cc: whatwg at whatwg.org
Subject: Re: [whatwg] Application deployment


On Tue, Jul 29, 2008 at 11:20 AM, Dave Singer <singer at apple.com> wrote:

Caching is on a full URL basis, of course.  Once that is decided, then yes,
I think that pre-cached items for a given URL are in the general cache for
that site.

A site that uses this feature is likely to be fragile. It will have to have
z.html both in the archive and available directly from the server, in case
z.html is requested before the load of the archive has finished. And if
those copies ever get out of sync you're in very big trouble, because
depending on the context, either the archive version or the direct version
is likely to consistently win the load race, so just occasionally some
clients will get the wrong version. This seems like a highly error-prone



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20080730/f933eee9/attachment-0001.htm>

More information about the whatwg mailing list