What is the status of the work-in-progress around the HTML5 AppCache that is in the repository? Is anybody actively working on that now? I'm interested in incorporating support for this feature into Chrome is why I'm asking. Michael
Michael Nordman <michaeln@google.com>, 2008-09-09 11:42 -0700:
What is the status of the work-in-progress around the HTML5 AppCache that is in the repository? Is anybody actively working on that now? I'm interested in incorporating support for this feature into Chrome is why I'm asking.
I'd been wondering the same thing myself, so I asked yesterday on #webkit on irc.freenode.net. The response from a couple of people there familiar with the code was that support for ApplicationCache (and I think in general for the offline-webapps part of the HTML5 spec) is on par with what's currently supported in Gecko. One limitation is that it doesn't support opportunistic caching -- but Gecko's implementation has the same limitation. --Mike -- Michael(tm) Smith http://people.w3.org/mike/
9 sep 2008 kl. 20.42 skrev Michael Nordman:
What is the status of the work-in-progress around the HTML5 AppCache that is in the repository? Is anybody actively working on that now? I'm interested in incorporating support for this feature into Chrome is why I'm asking.
Michael
Hey Michael! As far as the specification goes, the two big parts that aren't implemented are opportunistic entries, and dynamic entries. Also, all I/O is currently synchronous which is of course something that we'd like to avoid. The relevant code is (as you probably already know) in WebCore/loader/appcache, but also elsewhere in the loader, surrounded by #if ENABLE(OFFLINE_WEB_APPLICATIONS). The code hasn't received a lot of testing (given that the spec is fairly new and in flux). Some regression tests are in LayoutTests/http/ tests/appcache. Any feedback/comments you have is of course much appreciated! Anders
Hi Anders, Thnx for the pointers to the tests. I hadn't seen them. Honestly I think the spec needs to be revisited on this thing. The manifest update/validation scheme in particular has some real problems around opportunistic caching and dynamically added resources imo. But that aside for the moment... * Is this stuff built into shipping Safari or iPhone browsers yet? * Are any apps, to your knowledge, relying on this stuff yet? * About the current implementation in the tree. I noticed all of the I/O was sync, everything including the cached responses are stored in an SQLite database. Also noticed that when a page that references an appcache is loaded, all of the resources contained in that appcache are loaded into memory at page load time. I'm glad you guys don't consider that as 'done' :) What would you think of separating response storage (headers and bodies) from the logical structure of an appcache (set of entries and categories, namespace definitions, etc). SQLite is a reasonable choice for the logical structure. That database could contain keys to response bodies contained in another repository from which ResourceHandles could be loaded asynchronously. Michael On Wed, Sep 10, 2008 at 11:46 PM, Anders Carlsson <andersca@apple.com>wrote:
9 sep 2008 kl. 20.42 skrev Michael Nordman:
What is the status of the work-in-progress around the HTML5 AppCache that
is in the repository? Is anybody actively working on that now? I'm interested in incorporating support for this feature into Chrome is why I'm asking.
Michael
Hey Michael!
As far as the specification goes, the two big parts that aren't implemented are opportunistic entries, and dynamic entries.
Also, all I/O is currently synchronous which is of course something that we'd like to avoid. The relevant code is (as you probably already know) in WebCore/loader/appcache, but also elsewhere in the loader, surrounded by #if ENABLE(OFFLINE_WEB_APPLICATIONS).
The code hasn't received a lot of testing (given that the spec is fairly new and in flux). Some regression tests are in LayoutTests/http/tests/appcache.
Any feedback/comments you have is of course much appreciated!
Anders
On Thu, 9/18/08, Michael Nordman <michaeln@google.com> wrote:
* Is this stuff built into shipping Safari or iPhone browsers yet?
This feature shipped with iPhone OS 2.1. When you use "Add to Home Screen" from the "+" button on Safari for iPhone, a web application with a manifest defined (per the HTML5 spec) will be saved with any cached resources. Note that the manifest file *must* be served with the correct MIME type for this to work. There is no shipping version of Safari for Mac OS X or Windows that supports this feature yet. Dave
I've been using this feature on the iPod Touch. It works, but under some circumstances during a cache-manifest change, Safari will crash and will from then on always crash when loading that page, until I reset the iPod's software. I had what looks like the same problem on Safari 4 preview 2. David Kilzer wrote:
This feature shipped with iPhone OS 2.1. When you use "Add to Home Screen" from the "+" button on Safari for iPhone, a web application with a manifest defined (per the HTML5 spec) will be saved with any cached resources. Note that the manifest file *must* be served with the correct MIME type for this to work.
There is no shipping version of Safari for Mac OS X or Windows that supports this feature yet.
-- View this message in context: http://www.nabble.com/HTML5-Application-Cache-tp19398643p20000223.html Sent from the Webkit mailing list archive at Nabble.com.
On Oct 15, 2008, at 12:11 PM, VictorM wrote:
It works, but under some circumstances during a cache-manifest change, Safari will crash and will from then on always crash when loading that page, until I reset the iPod's software.
Would you be willing to file a bug report with some details and steps to reproduce? http://webkit.org/quality/reporting.html -- Darin
Please file a bug on <https://bugs.webkit.org/> with steps to reproduce on Safari. We really know what change(s) in the manifest caused the crash. Also I believe there was at least one recent manifest-related crash fix, so trying this on a WebKit nightly build (before filing a bug) would also be helpful. Thanks! Dave On Wed, 10/15/08, VictorM <vosuba@gmail.com> wrote:
I've been using this feature on the iPod Touch.
It works, but under some circumstances during a cache-manifest change, Safari will crash and will from then on always crash when loading that page, until I reset the iPod's software.
I had what looks like the same problem on Safari 4 preview 2.
David Kilzer wrote:
This feature shipped with iPhone OS 2.1. When you use
"Add to Home
Screen" from the "+" button on Safari for iPhone, a web application with a manifest defined (per the HTML5 spec) will be saved with any cached resources. Note that the manifest file *must* be served with the correct MIME type for this to work.
There is no shipping version of Safari for Mac OS X or Windows that supports this feature yet.
-- View this message in context: http://www.nabble.com/HTML5-Application-Cache-tp19398643p20000223.html Sent from the Webkit mailing list archive at Nabble.com.
_______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
participants (6)
-
Anders Carlsson
-
Darin Adler
-
David Kilzer
-
Michael Nordman
-
Michael(tm) Smith
-
VictorM