Don't use blocking transports for cron

[ryan]

Transports that do not support non-blocking mode can cause long delays when spawning cron. This is seen after publishing when cron blocks while processing pings.

Possible fixes:

• Prioritize non-blocking transports for non-blocking requests.
• Force cron to use fsockopen.

[ryan]

(In [9572]) Prioritize transports differently for non-blocking requests. fixes #8086

[DD32]

Did you by any chance forget to set the non-blocking transports for the GET branch?

foreach ( array('curl', 'streams', 'fopen', 'fsockopen', 'exthttp') as $transport ) {

vs

foreach ( array('streams', 'fsockopen', 'exthttp') as $transport ) {

[ryan]

get and post should return the same transports they did before, just in a different order if non-blocking. Post doesn't have as many transports as get.

[DD32]

oh.. Right! :) Here was I thinking that it wouldnt return a blocking transport at all for a non-blocking request. Its still early :)

[ryan]

Plugin that lists available transports in the admin footer.

[ryan]

Try integer timeout instead of float.

[ryan]

(In [10025]) Round timeouts less then 1 but greater than 0 to 1 for curl transport. see #8086