[wp-trac] [WordPress Trac] #14759: Improve the way oEmbed deals with caching

[WordPress Trac]

#14759: Improve the way oEmbed deals with caching
--------------------------+--------------------
 Reporter:  Viper007Bond  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  4.0
Component:  Embeds        |     Version:  3.0.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+--------------------

Comment (by markjaquith):

 [attachment:14759.2.diff] Institutes 1 day caching of valid results on the
 admin side. The front end will always serve from the cache, if available,
 but the backend will use valid cache responses (but not cached bad-
 responses "{{unknown}}") for one day. It also no longer purges the cache
 on every save. Good responses are cached regardless of post status. Cached
 {{unknown}} responses are used on the front end, but re-attempted on the
 backend. And bad responses never replace a good response.

 This should '''greatly''' reduce the outbound requests. Say you had a post
 with 10 tweets, and saved 10 drafts of it. Previously that would be 100
 oEmbed requests to Twitter.com. Now it's 10.

 What this doesn't address: that if you never update the post, the cache
 stays indefinitely.

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