[wp-trac] [WordPress Trac] #33276: redundant wp_using_ext_object_cache check in get/set_transient

[WordPress Trac]

#33276: redundant wp_using_ext_object_cache check in get/set_transient
--------------------------+--------------------------
 Reporter:  shmulikk      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Cache API     |     Version:  2.8
 Severity:  normal        |  Resolution:  wontfix
 Keywords:  close         |     Focuses:  performance
--------------------------+--------------------------
Changes (by hellofromTonya):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 Hello @shmulikk,

 Thank you for opening this ticket and contributing to the discussions. I
 hope the discussion helped.

 Closing this ticket. Why? The design is intentional, as @dion [comment:14
 explained the reasoning]:
 >The code is intentionally duplicated, as Transients are designed not to
 hit the database in the event that an object cache is in use (Whether that
 object cache is working correctly or not, is out of the hands of
 WordPress).

 [comment:14 This idea] might be one to consider, though I'd suggest
 opening a new ticket for it if there's interest.
 >A better way to approach this, I think, would be for for a object cache
 dropin to be able to notify WordPress that it's unhealthy and not working
 correctly, possibly by filtering `wp_using_ext_object_cache()` somehow.

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