HTML and CSS Reference
In-Depth Information
3. Browser: parses index.html , and all assets in the local
cache are served locally
4. Browser: request the manifest fi le from the server
5. Server: returns a 304 code notifying the browser that the
manifest hasn't changed
Once the browser has its cache of assets, it serves them locally
fi r s t a in d t h e in r e q u e s t s t h e m a in fi fi e s t . A s s h o w in fi in Figure 7.3 ,
Safari is loading all the assets for my time application, but at
the same time I'm monitoring the access log for the app, which
we can see only time.manifest and server-time.js is being
requested over the connection.
FIGURE 7.3 Safari makes a
request for the app loading
using the local cache and
requesting only the manifest
and server-time from the server.
This time, you re-request the
app—but the manifest has
changed. If the manifest has
changed, the process from
step 1 to 4 is exactly the same,
but next the browser needs to
reload the cache.
1.
Browser: re-requests http://introducinghtml5.com/
examples/ch07/time/
2.
Browser: detects that it has local cache for this page and
serves it locally
3.
Browser: parses index.html , and all assets in the local
cache are served locally
4.
Browser: request the manifest fi le from the server
5.
Server: returns the updated manifest fi le
Search WWH ::




Custom Search