Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:21312 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40287 invoked by uid 1010); 21 Dec 2005 23:04:04 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 40272 invoked from network); 21 Dec 2005 23:04:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Dec 2005 23:04:04 -0000 X-Host-Fingerprint: 64.233.184.206 wproxy.gmail.com Linux 2.4/2.6 Received: from ([64.233.184.206:16937] helo=wproxy.gmail.com) by pb1.pair.com (ecelerity 2.0 beta r(6323M)) with SMTP id 74/74-14561-46FD9A34 for ; Wed, 21 Dec 2005 18:04:04 -0500 Received: by wproxy.gmail.com with SMTP id i24so245814wra for ; Wed, 21 Dec 2005 15:04:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N+e5ITrEUll3Q4egwxtTgI8UkRKpGF/ygRPeCtY9adn9fX9QercnflCjQNT9BR2MvnB8WtnLenQD3ySEnyePM8rDdaqOB2RsltY/he/usVIVGrH+iLMfbQUm20CSoW4IuUc23F5DlflOsu/1qkFrnNMZGlCVucGsoI2aqW7qm30= Received: by 10.54.96.2 with SMTP id t2mr1097275wrb; Wed, 21 Dec 2005 15:03:58 -0800 (PST) Received: by 10.54.77.20 with HTTP; Wed, 21 Dec 2005 15:03:59 -0800 (PST) Message-ID: <4e89b4260512211503n345ad4d1o14e7eb983c136b25@mail.gmail.com> Date: Wed, 21 Dec 2005 18:03:59 -0500 To: Andreas Schiffler Cc: internals@lists.php.net In-Reply-To: <43A9BCFA.8010902@ferzkopp.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A979A4.80307@ic-agency.com> <4e89b4260512211120u47f72a80jf91f0d9e74d1791e@mail.gmail.com> <43A9BCFA.8010902@ferzkopp.net> Subject: Re: [PHP-DEV] Change to timeout use From: kingwez@gmail.com (Wez Furlong) On 12/21/05, Andreas Schiffler wrote: > >There's not much difference between .25 and 1 second. > Ah, this may be so for the traditional use of webservices. But for > eCommerce applications for example speed is king and its also very > important to provide consistent speeds (i.e. not hang). I don't have > published reference links on this, but some of our private documents > point to a target of max. 200ms for an ad-serving related webservice > (which is technically absolutely feasable anyhow, even across the country= ). OK, but this is in the case where you've got an error, right? What do you do if you don't get a response, and how often does it happen? > OK. I understand that. I'll try my best to come up with a patch set then. > Can someone point me to some documentation on how to do this? Is > someone willing to assist me in making this patch? It sounded like you'd identified all the places that needed adjusting; just go ahead and try making it work :) You can ask questions here on internals@ and I'm sure you'll get some help if you ask the right questions (try to be as specific as possible so it's easier to answer). Hope that helps :) --Wez.