[wp-trac] [WordPress Trac] #17210: Massive duplication of oEmbed postmeta

[WordPress Trac]

#17210: Massive duplication of oEmbed postmeta
------------------------------------+-----------------------------
 Reporter:  archon810               |       Owner:  Viper007Bond
     Type:  defect (bug)            |      Status:  reopened
 Priority:  normal                  |   Milestone:  Future Release
Component:  Embeds                  |     Version:  3.1
 Severity:  normal                  |  Resolution:
 Keywords:  has-patch dev-feedback  |
------------------------------------+-----------------------------
Changes (by helenyhou):

 * keywords:  has-patch dev-feedback punt => has-patch dev-feedback
 * milestone:  3.5 => Future Release


Comment:

 Replying to [comment:26 ryan]:
 > I'd like to get rid of the big non-autoload values that end up in
 options, not add more.
 >
 > As things get pushed out of the cache we could see lots of oembed
 refetch activity on a busy site.

 I said approximately the same thing to wonderboymusic myself, just not as
 well :) Pointed out that, for example, Twitter has a relatively low rate
 limit based on IP, which already quickly runs out on a shared host and for
 a user who embeds a bunch of tweets in one post and either leaves the
 editor open or saves small changes a bunch of times (anything that
 triggers save_post). Triggering even more of those requests on the front
 all at once because of expiration would not end well.

 Would love to see a better solution, but don't think an expiring transient
 is it. Also a bit late for 3.5.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/17210#comment:30>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software