- From: Ming, Bai <bai.ming@intel.com>
- Date: Wed, 24 Apr 2013 09:32:03 +0800
- To: Alexandre Morgaut <Alexandre.Morgaut@4d.com>
- CC: "Long, Xiang" <xiang.long@intel.com>, "Min, Hongbo" <hongbo.min@intel.com>, "Marcos Caceres (w3c@marcosc.com)" <w3c@marcosc.com>, "public-sysapps@w3.org" <public-sysapps@w3.org>
> I think that listing the HTML files to be parsed in the manifest could solve this and would be more acceptable for a developer > > ex: > > checkForAppCache: [ > '/main.html', > '/special.html' > ] Absolutely agree. It's better to have one thing to be done in only one place. > > It would be part of the process when adding or removing a module, and such process is already done by package developers when they list dependencies > > >> For multiple cache manifest paths, is it possible for web developers to use a same cache manifest for different pages? Like: >> /main.html >> <html manifest="myapp.manifest"> >> ... >> /special.html >> <html manifest="myapp.manifest"> >> ... > It is technically possible to reference the same myapp.manifest and could be ok when such html files only belong to this app > But it is not imaginable for an HTML module shared among different apps > > You can imagine special receiving messages to process from main with specific UI interactions. If special is updated and requires changes in its appcache, it is hard to ask to all the dependent apps to update their own appcache instead. Should we be considering the incompatible between two or more 'myapp.manifest's since different html files can have their own manifest. e.g. //myapp1.manifest CACHE MANIFEST index.html NETWORK server.cgi //myapp2.manifest CACHE MANIFEST server.cgi NETWORK index.html -- Regards, Bai
Received on Wednesday, 24 April 2013 01:30:47 UTC