[wp-trac] [WordPress Trac] #22205: Plugin updater - Optimize API Request

WordPress Trac noreply at wordpress.org
Thu Oct 25 19:45:33 UTC 2012


#22205: Plugin updater - Optimize API Request
-----------------------------+------------------------------
 Reporter:  logikal16        |       Owner:
     Type:  enhancement      |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:  has-patch        |
-----------------------------+------------------------------

Comment (by logikal16):

 Points taken, with a few follow-ups:

 1. Which fields are used by api.wordpress.org?
 2. When determining the plugin, it makes sense for api.wordpress.org to
 use the plugin slug, since it's unique to WP.org and can't be tampered
 with (unlike "Title" or "Name"). How does the API currently identify a
 plugin?
 3. For sites with dozens of plugins, the request size isn't negligible.

 While this isn't urgent by any means, it's a low-hanging-fruit that would
 conserve resources at both ends of the API request.

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


More information about the wp-trac mailing list