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

WordPress Trac noreply at wordpress.org
Wed Feb 26 21:29:09 UTC 2014


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

Comment (by helen):

 Replying to [comment:40 markjaquith]:
 > * Could we recognize oEmbed URLs client-side in the editor and
 proactively fire AJAX cache requests before the post is even saved with
 that URL?

 I think this would go a long way toward solving the initial publish
 problem, and since I also think we should prepare ourselves for a
 view/preview of sorts even if we don't tackle it this release (although we
 should probably do at least part of #15490 if we land this soon), we might
 as well at least do the caching part.

 > * Should we be doing TLC transients style soft expiration, obeying the
 oEmbed cache time if it provides one and using a long cache time (a year)
 otherwise?

 I'm not sure how much I really care about oEmbed expiry, especially if we
 go with only replacing cache values when a valid response is returned and
 continue with only doing it on post save (or rather, firing the call to do
 it after post save).

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


More information about the wp-trac mailing list