- From: <bugzilla@jessica.w3.org>
- Date: Mon, 05 Dec 2011 22:10:30 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14702
Tab Atkins Jr. <jackalmage@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jackalmage@gmail.com
--- Comment #21 from Tab Atkins Jr. <jackalmage@gmail.com> 2011-12-05 22:10:28 UTC ---
(In reply to comment #20)
> It's really not clear to me, given this, why anyone would want to use the mixed
> structure and data model these days. It's harder to maintain, is no faster than
> the split model, and if you use appcache, is forcibly slower.
>
> Given how many people are asking for this, it seems reasonable that we should
> consider how to add the feature, but as far as I can tell it is never the right
> solution from an authoring perspective.
The "split model" requires authors to fundamentally change how they author
pages, so that most of the useful parts of the page are generated from JS based
on an external data file.
Some authors do indeed embrace this model, but the vast majority still do not -
they generate the pages whole on the server-side and then send them to the
client. Changing to the split model requires pretty substantial changes to the
authoring workflow and often substantial amounts of code rewriting. It also
means that an accidental JS error takes down the whole site, rather than just
killing some functionality, which is often not enough to render the site
unfunctioning as a whole.
Authors shouldn't have to substantially change their coding practices to
benefit from caching.
To be very specific about the use-case, it is to take an existing page authored
using current standard practices and make it offline-capable with a minimum of
changes to the site's structure, without interfering with normal online
interactions. The external resources for the site should be all cached
together or not cached at all, so that pages don't half-load and end up looking
or acting broken (this is the failure-mode of relying on the HTTP cache).
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 5 December 2011 22:10:37 UTC