14445 2011-10-13 08:59:58 +0000 When dealing with large web applications there should be a way to just do delta downloads of modified files. Just making a small change to e.g. a JS file and modifying the manifest file will currently result in a complete re-downloading of the entire appl 2011-10-24 18:44:08 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#downloading-or-updating-an-application-cache P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 58181 0 contributor 2011-10-13 08:59:58 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html Multipage: http://www.whatwg.org/C#downloading-or-updating-an-application-cache Complete: http://www.whatwg.org/c#downloading-or-updating-an-application-cache Comment: When dealing with large web applications there should be a way to just do delta downloads of modified files. Just making a small change to e.g. a JS file and modifying the manifest file will currently result in a complete re-downloading of the entire application. Posted from: 155.250.128.34 User agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/534.51.22 (KHTML, like Gecko) Version/5.1.1 Safari/534.51.22 58774 1 ian 2011-10-24 18:44:08 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: I agree, but that seems like an HTTP issue, not an HTML issue. HTTP should support this in general for all cache update requests. I recommend bringing this up with the HTTP WG.