The problem isn't the duration of the soap query call, it's how long to wait before giving up on establishing the connection. The connect timeout is completely independent from the soap call duration or the work that it performs.
--Wez. On 12/21/05, steve <[EMAIL PROTECTED]> wrote: > > There's not much difference between .25 and 1 second. > > Actually, there is. It depends on the length of time of a typical page > request (and the proportion of the delay to the typical time), and the > hardware setup to handle that. The 4x slowdown can cause a cascade > effect as it might cause more than 4x simultaneous connections on the > target (causing it to slow down, and the problem to keep growing). > That gets amplified by the number of webservers a bit. > > I don't use SOAP in such a way, but it is analogous to MySQL queries, > and having a 1s time for a common query can lead to all sorts of > problems. > > The reason I'm chiming in here is to suggest that if this is looked > at, that it be made universal for all network timeouts. I'm thinking > MySQL in particular, as there could be a class of websites that don't > use custom connection pooling handlers on their webservers to get > around this (useful, for example, if switching to backup servers). > > So maybe fractional seconds for network related timeouts could be a > wishlist item for PHP 6? > > Personally, I wouldn't mind connection pooling too. I like to dream... > > :) > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
