[wp-trac] [WordPress Trac] #8622: HTTP API Fallover & non-blocking order doesnt appear to be working

[WordPress Trac]

#8622: HTTP API Fallover & non-blocking order doesnt appear to be working
------------------------------+-----------------------------
 Reporter:  DD32              |       Owner:  jacobsantos
     Type:  defect (bug)      |      Status:  reopened
 Priority:  normal            |   Milestone:  Future Release
Component:  HTTP              |     Version:  2.7
 Severity:  normal            |  Resolution:
 Keywords:  has-patch tested  |
------------------------------+-----------------------------

Comment (by dd32):

 > As for unit testing,

 Very simple to do. Filter the ::test() methods to select which transport
 you wish to test, test, remove filters, rinse repeat.

 My suggestion here is to push the changes needed through #16870,
 specifically, when a transport fails, progressivly mark it as unusable.

 The alternative is to adding an extra parameter similar to the block of
 code [http://core.trac.wordpress.org/attachment/ticket/8622/8622.4.diff
 starting line 206 in this patch], which would be purely for a plugins
 usage.

 In core we're striving for a HTTP API which just works, plugin authors
 shouldn't have to do anything more than request it, and handle an error
 condition being returned, but at the same time, it shouldn't cause
 unnecessary slowdowns for the user, failing over to the next transport
 over and over on a plugin's request should not be possible.

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