Closed
Bug 6627
Opened 25 years ago
Closed 25 years ago
Reload Policy
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
M13
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!
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.
Comment 6•25 years ago
|
||
There was a thread on the npm.netlib newsgroup about how to do this that seemed
to reach some agreement.
Updated•25 years ago
|
Target Milestone: M12 → M13
Comment 7•25 years ago
|
||
Moving what's not done for M12 to M13.
Bulk move of all Cache (to be deleted component) bugs to new Networking: Cache
component.
Updated•25 years ago
|
Assignee: warren → gagan
Comment 9•25 years ago
|
||
back to Gagan
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Comment 10•25 years ago
|
||
*** This bug has been marked as a duplicate of 14772 ***
Comment 11•25 years ago
|
||
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.
Description
•