GWT HTML5 offline web-application dynamic manifest

Question

I have recently converted one GWT web application to be capable to work in HTML5 offline mode. So far seems to work fine but I'm wondering if it's a good idea to serve different cache.manifest versions for different browsers?

As we know, GWT will need only one permutation for one target browser (in case of one language, let's make it simple). And it's obvious that we would need to download just one XXXXXX.cach.html for one target browser.

I see it's possible as on the serverside I could check User-Agent HTTP header and return contents of the appropriate version of my cache.manifest, accordingly setting all headers in order not to break offline status checking behavior. The rest of resources would be served with no custom filtering.

Is this a good idea to optimize it this way? Is there anything I could be missing?

Answer 1

By accident, I came across the following project: Mobile GWT. Quick documentation (HTML5 Manifest) and code (HTML5ManifestServletBase) review reveals that manifest is prepared considering each client, so that only required resources are sent over the network. Pity,- I was just about to make my own open source solution...