[wp-trac] [WordPress Trac] #14786: It's WP_Http_ExtHTTP not WP_Http_ExtHttp

[WordPress Trac]

#14786: It's WP_Http_ExtHTTP not WP_Http_ExtHttp
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:                        
     Type:  defect (bug)  |      Status:  new                   
 Priority:  normal        |   Milestone:  Awaiting Review       
Component:  HTTP          |     Version:  3.0.1                 
 Severity:  normal        |    Keywords:  has-patch dev-feedback
--------------------------+-------------------------------------------------

Comment(by hakre):

 Replying to [comment:12 dd32]:
 > > From what I read (but please double check) both have the same order.
 >
 > It was meant as a background as to why there were 2 functions, The
 ordering has been played with over the lifetime of WP_HTTP as bugs poped
 up here and there.

 So what do you would say? Is it a need to have multiple transport orders
 per context for the future? If so, we can add a filter onto the array
 probably and/or make it a parameter.

 Adding a filter would help to easily let plugins control the available
 transports and even add own ones. Hey I like that idea. Currently it's not
 possible and control is a bit akward
 ([http://core.trac.wordpress.org/attachment/ticket/11499/11499-curlforce.php
 forcing curl plugin example]).

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