[wp-trac] [WordPress Trac] #22661: Allow object caches to degrade gracefully

[WordPress Trac]

#22661: Allow object caches to degrade gracefully
--------------------------+-----------------------------
 Reporter:  markjaquith   |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:  Future Release
Component:  Cache API     |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  2nd-opinion   |     Focuses:
--------------------------+-----------------------------

Comment (by mpvanwinkle77):

 As far as design goes, I generally agree with @jipmoors that, given the
 WordPress API, any class "overloading" should take place in the context of
 a filter and NOT simply placing the file in a certain location.This change
 would solve both this issue and the rather clumsy way that external object
 caches are currently installed which can be problematic on locked-down
 filesystems. This comment isn't intended to block this patch but only to
 suggest a ticket for overhauling this in the future. Obviously the
 implementation would have to be to respect the file-based overloading
 first so as not to create any backward compatibility issue. But over time
 that approach could be deprecated.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/22661#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform