Re: cvs: php-src /main/streams streams.c transports.c xp_socket.c
| From: | Wez Furlong | Date: | Thu, 05 Feb 2004 01:36:43 +0000 |
| Subject: | Re: cvs: php-src /main/streams streams.c transports.c xp_socket.c | ||
| References: | 1 2 3 4 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-26030@lists.php.net to get a copy of this message | ||
It should be more like 4.2.x and return in a very short time;
it returns immediately for me using php5 + my patch.
Is your default_socket_timeout set to 30 seconds?
--Wez.
----- Original Message -----
From: "Jani Taskinen" <sniper@iki.fi>
To: "Wez Furlong" <wez@thebrainroom.com>
Cc: "Wez Furlong" <wez@php.net>; <php-cvs@lists.php.net>
Sent: Thursday, February 05, 2004 1:31 AM
Subject: Re: [PHP-CVS] cvs: php-src /main/streams streams.c transports.c
xp_socket.c
>
> I'm propably missing the point..but that test completes
> without any errors in ~30 secs with latest builds of both
> PHP_4_3 and HEAD. (HEAD without your patch does exactly same..)
>
> (propably irrelevant, but with 4.2.3 it completes in less
> than a second, also without any errors)
>
> --Jani
>
> On Thu, 5 Feb 2004, Wez Furlong wrote:
>
> >Possibly :)
> >I found the code hanging around in my tree after being there for a week
or
> >more;
> >I can't remember what I was working towards when I wrote it, and I'm a
> >little
> >too busy to check into it right now.
> >
> >Try this with php4.3:
> >
> >php -r '$fp = pfsockopen("localhost",80); $fp =
pfsockopen("localhost",80);'
> >
> >the patch needs MFH'ing if that takes ~60 seconds to complete with no
> >error message; I'll merge it if it needs doing (it won't be simple since
> >the guts have changed from 4.3 to 5).
> >
> >--Wez.
> >
> >----- Original Message -----
> >From: "Jani Taskinen" <sniper@iki.fi>
> >To: "Wez Furlong" <wez@php.net>
> >Cc: <php-cvs@lists.php.net>
> >Sent: Thursday, February 05, 2004 12:53 AM
> >Subject: Re: [PHP-CVS] cvs: php-src /main/streams streams.c transports.c
> >xp_socket.c
> >
> >
> >>
> >> Does this fix have possibly anything to do with bug #26863 ??
> >> And how about doing a nice little MFH?
> >
> >
>
>
>