Too short timeout for trackbacks and pingbacks

Description

The timeout for trackback and pingback set on line 201 of wp-includes/cron.php is too short (0.01). I think this is the reason why many servers aren't able to do pingbacks and trackbacks. Maybe this value should be set to 1 or be available in the settings page to change to fit the needs of the server..

The request is meant to be async so we want a short timeout. Some of our transports might not be handling that well, however. curl, for example, bumps any timeout less than 1 to 1 because it doesn't like floats. Other transports may have a similar problem.

I've seen multiple wp-blogs not working fine with timeout of 0.01 seconds so they needed to patch up the time. Mostly it is not possible to change the hardware / transport / whatever so there has to be a solution on software side.

Thats the reason I would definitly increase this value. One has to try out how much is needed and how much is possible without slowing down everything. For me personally one second is working very fine and everyone else giving feedback to my hint confirmed this.

So please increase this limit in the earliest future release / update to get the pingbacks working without manually patching of the files.

I doubt the timeout is going to be increased. Theres simply no need for it. However, Any transports which are not handling properly with a low connection timeout do need to be updated, Like Ryan said.

Unfortunately, Patchers cant tell what is causing it on the target system without actually getting feedback, Without feedback, We cant reproduce, AFAIK, this hasnt been reproduced either, other than with Curl which was fixed..