[wp-trac] [WordPress Trac] #33055: Support Parallel HTTP Requests in WP_Http, et al

WordPress Trac noreply at wordpress.org
Mon Jun 13 17:24:04 UTC 2016


#33055: Support Parallel HTTP Requests in WP_Http, et al
----------------------------------------+--------------------------
 Reporter:  wonderboymusic              |       Owner:  rmccue
     Type:  task (blessed)              |      Status:  assigned
 Priority:  high                        |   Milestone:  4.6
Component:  HTTP API                    |     Version:
 Severity:  normal                      |  Resolution:
 Keywords:  needs-patch needs-dev-note  |     Focuses:  performance
----------------------------------------+--------------------------

Comment (by mordauk):

 I'm also going to echo the sentiments of concern regarding the breaking
 changes.

 Since I work primarily in eCommerce, I'll use that as my example. Easy
 Digital Downloads, and numerous other eCommerce plugins, use the WP HTTP
 API for handling remote requests to merchant processors. I know that my
 team has always expected responses to be arrays since day one. That's what
 WordPress gave us so that's what we used.

 I went through all of our plugins today and updated them to be fully
 compatible with both the current and the newly proposed versions.

 '''I am not the typical plugin developer'''. I pay attention to trac and
 the make blogs so that I know these kind of changes are happening, but
 most plugin developers will never have known this change is coming and
 that could result in really bad and unforseen consequences.

 While using `ImplementArrayAccess` does take care of a lot of cases, there
 are always going to times when request responses were strictly checked for
 `is_array`. When that happens, the request process '''will fail'''.

 In the realm of eCommerce, that could potentially means ridiculously large
 numbers of failed or missed transactions, and that is a risk I simply do
 not believe is justified.

 I love what the new version provides and I really want to see it move
 forward, but I feel it needs to happen in multiple steps, not one giant
 and abrupt change.

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


More information about the wp-trac mailing list