- From: Tobie Langel <tobie@fb.com>
- Date: Wed, 19 Sep 2012 12:37:22 +0000
- To: Tobie Langel <tobie@fb.com>, Jake Archibald <jaffathecake@gmail.com>
- CC: "public-fixing-appcache@w3.org" <public-fixing-appcache@w3.org>
On 9/11/12 5:04 PM, "Tobie Langel" <tobie@fb.com> wrote: >On 9/11/12 4:26 PM, "Jake Archibald" <jaffathecake@gmail.com> wrote: > >>The zip file method provides the packaging, but isn't as efficient the >>current appcache system when it comes to updates. > >Agreed. It's aimed mostly at static content (where "static" means "rarely >changing"). > >>If I want to update >>a js file I can change the manifest to point at the new js file. if >>I've been smart with caching headers, only the js file will be >>downloaded. The zip system means downloading the whole package again >>for any change, depending on the situation this could be a large >>download for a small change. Actually, turns out gzip now has an rsyncable mode in some distributions. This would allow sending diffs of zipped files across the wire. This could be done at the application level, or at the HTTP level if the proposal to include diffs at the HTTP level gets sufficient traction. --tobie
Received on Wednesday, 19 September 2012 12:37:51 UTC