Skip to main content

Appcache manifest file issues/caveats


Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Most important coding caveats about the manifest file and appcache.

  • The main html file that declares the manifest is ALSO cached in app cache, even if it is not defined in CACHE section. So, if you update the html itself (master),  in the manifest must change (a update-time-stamp) to see the changes (also will require user refresh or swapCache call)
  • If the master is rendered from server and it has varying (seeded or dynamic) parameters, a separate copy of the html is stored in appcache per canonical url (index.php?q=search1, index.php?q=search2 will have separate cached html). This is generally unnecessary, but if you do want to have parameters to pass to javascript, ensure that it is passed via location.hash(e.g: index.php#!q=search1)
  • Manifest file must begin with the line "CACHE MANIFEST" instruction. Empty lines are treated just like comments in some browsers, so ensure it is the first one
  • Manifest file must  be served with a text/cache-manifest MIME type. Chrome seems to be fine otherwise, but you dont write for chrome alone, do you?
  • Manifest file must  be encoded with 8-bit Unicode Transformation Format (UTF-8) character encoding. This is as per W3C stature, may be easy to do, before you find yourself in trouble.
  • The path URLs in CACHE section cannot have wildcards. (qualified - relative, canonical and external urls for each resource must be defined separately). URLs in  NETWORK and FALLBACK sections can have wildcards (/api will apply for api directory tree; /api/1.html and /api/2.html but not /api2 or /api2/1.html) .
  • URLs defined in CACHE are all or nothing. This is probably the biggest issue when you use external URLs, your app is now at the mercy of the availability and correct-ness (at the time of caching) of the external providers.
  • Preferred extension for file is .appcache, however, browsers seem to be fine with anything.
  • more in gotchas in get-offline, and here.

Labels:

Popular posts from this blog

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.
Read More >>

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>
Read More >>