913828 - HTTP cache v2: remove the old (Darin's) cache code

Status: RESOLVED DUPLICATE of bug 1694662

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

Comment 5

[amar.lakshya]

Honza, I think this should be dealt with. All the dependencies are resolved. Should I touch it?

Comment 6

[Honza Bambas (:mayhemer)]

(In reply to amar.lakshya from comment #5)
> Honza, I think this should be dealt with. All the dependencies are resolved.
> Should I touch it?

I don't understand the question.  Removing the old backend is blocked by removing the appcache (aka Offline Application Cache) that is still used by some big players.

So, no, don't touch anything please, unless I just misunderstand your question :)

Comment 7

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 8

[Firefox Bug Husbandry Bot]

Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258

Comment 9

[u597032]

(In reply to Honza Bambas (:mayhemer) from comment #6)
> (In reply to amar.lakshya from comment #5)
> > Honza, I think this should be dealt with. All the dependencies are resolved.
> > Should I touch it?
> 
> I don't understand the question.  Removing the old backend is blocked by
> removing the appcache (aka Offline Application Cache) that is still used by
> some big players.
> 
> So, no, don't touch anything please, unless I just misunderstand your
> question :)


I thought appcache should be/has been removed. Am I wrong?

Comment 10

[Honza Bambas (:mayhemer)]

No, there are few big players still using it, unfortunately.  When the SW API is major enough to replace appcache, we may deprecate (aka disable) by default.  Then remove, eventually.