This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 15771 - appcache: avoid out-of-sync situations or cache busting when using appcache with non-sticky load balancers
Summary: appcache: avoid out-of-sync situations or cache busting when using appcache w...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Robin Berjon
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-29 11:30 UTC by Tobie Langel
Modified: 2013-04-24 16:21 UTC (History)
5 users (show)

See Also:

Attachments

Description Tobie Langel 2012-01-29 11:30:14 UTC 
Use case / explanation: 

An application is hosted on a cluster of servers behind a non-sticky load
balancer. It is updated daily. Even though all servers are not updated
instantly and two versions of the application co-exist for a while, it is
possible to update the application without risking to have an out-of sync
version of the application (e.g. manifest file and assets of the latest version
combined with a Master Entry of the previous version) or to need to invalidate
the cache to avoid such issues.
Comment 1 contributor 2012-07-18 06:55:03 UTC 
This bug was cloned to create bug 17820 as part of operation convergence.
Comment 2 Robin Berjon 2013-01-21 16:00:29 UTC 
Mass move to "HTML WG"
Comment 3 Robin Berjon 2013-01-21 16:03:10 UTC 
Mass move to "HTML WG"
Comment 4 Robin Berjon 2013-04-24 16:21:27 UTC 
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: none
Rationale: This will be addressed by NavCon.