[wp-trac] [WordPress Trac] #25738: WP_HTTP uses transports that incorrectly claim to support a request
WordPress Trac
noreply at wordpress.org
Sat Nov 16 00:57:56 UTC 2013
#25738: WP_HTTP uses transports that incorrectly claim to support a request
--------------------------+------------------
Reporter: dd32 | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: 3.8
Component: HTTP | Version:
Severity: normal | Resolution:
Keywords: |
--------------------------+------------------
Comment (by rmccue):
Replying to [comment:10 dd32]:
> I have been considering for a while of changing the order to Streams
first for all connections.
See also comment:2 ;)
> Streams also has the benefit that it's supposably better at non-blocking
connections (well, it doesn't block the connection for long..).
> It may also mean that we start getting more bug reports for it, and we
realise it's not as reliable as we previously believed (although I find
this unlikely).
cURL has a fairly large install base, and the advantage of handling more
in C gives us better performance. Adding parallel request support would
help with this, but I don't think anyone has proposed that yet.
> Changing the order has implications elsewhere though, as a result, I
wouldn't want to change the order unless we also added a parameter to try
both transports before failing (ie. for Update-related stuff), which I
think would be good regardless.
I'm not sure special-casing it is a good idea; more options = worse.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/25738#comment:11>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list