Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:10972 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 81499 invoked by uid 1010); 8 Jul 2004 07:45:41 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 81475 invoked by uid 1007); 8 Jul 2004 07:45:41 -0000 Message-ID: <20040708074540.81462.qmail@pb1.pair.com> To: internals@lists.php.net Reply-To: "Pan qingfeng" References: <4e89b4260407050538460acfee@mail.gmail.com> <20040705141455.99532.qmail@pb1.pair.com> Date: Thu, 8 Jul 2004 15:47:14 +0800 Lines: 76 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Posted-By: 218.19.158.229 Subject: Re: [PHP-DEV] CVS Account Request: pqf From: pqf@tebie.com ("Pan qingfeng") Hi, Derick Please visit http://fastcgi.coremail.cn, source code and doc there ^_^ Thanks Qingfeng Pan "Derick Rethans" ???? news:Pine.LNX.4.58.0407080931160.11582@localhost... > Hey, > > sounds cool, do you have any code to show as I'm interested in trying it > out. > > regards, > Derick > > > On Mon, 5 Jul 2004, Qingfeng Pan wrote: > > > There are some advantages... > > a) mod_fastcgi talk to PHP process with TCP socket, but this module use > > UNIX domain socket(or named pipe on Win32) instead. PHP with TCP socket will > > make Fastcgi-PHP not workable on Win32 (bug #27515 php -b still not > > working). With the new module, -b options is *NOT* necessary, because it's > > now using named-pipe on Win32. I have tested the binary Win32 Installer > > downloaded from official website. > > On the other hand, the performance is better while using UNIX domain > > socket on UNIX platform. > > With mod_fastcgi, you will have to run Fastcgi-PHP separately from the > > web server in UNIX box. That mean you have to start some PHP processes > > before Apache start, it's not a big deal, but not that "pure" like mod_php. > > > > b) Spawn PHP process dynamically, that mean spawn a PHP process ONLY when > > incoming a new request or there is no enought FastCGI process. With > > mod_fastcgi PHP, you have to run PHP separately and specify the PHP process > > number at the very beginning. > > > > c) Corrupt process detecting. With mod_fastcgi, every request is commucating > > throught a single TCP port, that mean the worker thread(or prefork process) > > of Apache does NOT know which FastCGI PHP process it's talking to. If there > > is something wrong with the PHP script, the worker thread knows there is a > > corrupt process there, but it can't tell which one is, > > With the new module, every fastcgi PHP process has a unique path > > listening on. That makes it easy to kick out the corrupt fastcgi server. > > > > "Wez Furlong" ???? > > news:4e89b4260407050538460acfee@mail.gmail.com... > > > We already have a fastcgi module... why do we need another apache2 > > > specific thing? > > > > > > --Wez. > > > > > > On 5 Jul 2004 05:43:47 -0000, Qingfeng Pan wrote: > > > > add an Apache2 fastcgi module for PHP(fastcgi.coremail.cn), I hope it > > will be released with PHP 5.1 branch > > > > > > > > -- > > > > PHP Internals - PHP Runtime Development Mailing List > > > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > > > > > > > >