[wp-trac] [WordPress Trac] #16624: Cache for WP_HTTP

WordPress Trac wp-trac at lists.automattic.com
Wed Mar 23 01:04:37 UTC 2011

#16624: Cache for WP_HTTP
 Reporter:  akshay_raje                    |       Owner:
     Type:  feature request                |      Status:  new
 Priority:  normal                         |   Milestone:  Awaiting Review
Component:  HTTP                           |     Version:
 Severity:  normal                         |  Resolution:
 Keywords:  2nd-opinion needs-patch close  |
Changes (by dd32):

 * keywords:  2nd-opinion needs-patch => 2nd-opinion needs-patch close


 IMO, This should be left to plugins to handle. Specifically, if a plugin
 requests a document, it needs to parse it and then cache the result

 Many uses of WP_HTTP is for data which should not be cached, only the
 parsed response.

 For example, API's in !WordPress parse the response and then cache that
 result. Feeds are requested, parsed, and then cached. File downloads
 shouldn't be cached, etc.

 Caching the whole result when a plugin only needs a small segment is also
 just going to end up caching more than is needed.

 Of course, there will be plugins which require the entire document to be
 cached, but they're in a minority compared to most uses of the API IMO.

Ticket URL: <http://core.trac.wordpress.org/ticket/16624#comment:2>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list