[wp-trac] Re: [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:  anonymous
     Type:  defect                   |       Status:  new      
 Priority:  normal                   |    Milestone:  2.7.1    
Component:  General                  |      Version:  2.7      
 Severity:  normal                   |   Resolution:           
 Keywords:  has-patch needs-testing  |  
-------------------------------------+--------------------------------------
Comment (by jacobsantos):

 I think it is the wrong path to use the same method in Fsockopen, because
 I think it is totally hackish way of going about it. I think it might be
 better, instead, to return the entire array and cycle through each one.
 The reason I didn't do this before was that a great deal of the API
 changed and I was unsure of where in the execution to put the code. The
 second reason would be that the worse case performance would be entirely
 terrible.

 Also, the HTTP API shouldn't fail where other transports succeed. If one
 fails, then it should be reasonable to say that all of the others will
 also fail.

 More hooks should be introduced to allow for a plugin to take hold and
 allow for more control. The issue is that anything done will introduce
 more performance overhead and slow the API down.

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