Closed Bug 6627 Opened 26 years ago Closed 25 years ago

Reload Policy

Categories

(Core :: Networking: Cache, defect, P3)

x86
All
defect

Tracking

()

VERIFIED DUPLICATE of bug 14772

People

(Reporter: gagan, Assigned: gagan)

References

Details

Work out an extensible and clean mechanism for reload policy handling for images, caching, etc. A lot of bugs are related to this one. I am just adding this to keep it on the table. If someone wants to jump in and contribute/volunteer feel free!
*** Bug 5058 has been marked as a duplicate of this bug. ***
Status: NEW → ASSIGNED
Target Milestone: M8
Pushed past necko landing...
Target Milestone: M9 → M10
Deferred till cache works in Necko.
Target Milestone: M10 → M12
I think the load groups should be able to handle this correctly now. However I would leave this open till cache lands and things work fine.
Assignee: gagan → warren
Status: ASSIGNED → NEW
Moving Assignee from gagan to warren since he is away.
There was a thread on the npm.netlib newsgroup about how to do this that seemed to reach some agreement.
Target Milestone: M12 → M13
Moving what's not done for M12 to M13.
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache component.
Assignee: warren → gagan
back to Gagan
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
*** This bug has been marked as a duplicate of 14772 ***
Verified duplicate of 14772. Bug 14772 and bugs marked dupe of 14772 seem to focus on reload policy through proxy but it covers 4.x parity reload policy.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.