Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49612
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:references:in-reply-to:subject:date:message-id:mime-version
         :content-type:content-transfer-encoding:x-mailer:thread-index
         :content-language;
        b=DtlfVIlVwkOXDcQ4k65JXGGk2nVwjsWFvtT8Vksz+cPRRw3oGvKQgFwhWYA1ZB/Ui8
         RU27bBDd+8LJDxT74IctHQCCqWJFYHvzYVCy1nvnQxCL02jLABW1F2ftfiD8oMzWwS4c
         8ea69k9FUNFnyh23cOvbCt6gcGwBhEahhHphc=
To: "'FGM at GMail'" <fgmarand@gmail.com>,
	<internals@lists.php.net>
References: <AANLkTimWkEEUoCvEGbb_a3zu5exiQa5p1YA9vrEPNPr6@mail.gmail.com>
In-Reply-To: <AANLkTimWkEEUoCvEGbb_a3zu5exiQa5p1YA9vrEPNPr6@mail.gmail.com>
Date: Mon, 13 Sep 2010 20:56:58 +0800
Message-ID: <000301cb5343$2cb0f560$8612e020$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHouSrFT9jA8IINKAjN9dq1+/H8upLVE4Hw
Content-Language: zh-cn
Subject: =?gb2312?B?tPC4tDogW1BIUC1ERVZdIFdTR0ktbGlrZSBTQVBJIGZvciBQSFAgPw==?=
From: gaochunhui@gmail.com (=?gb2312?B?uN+0urvU?=)

Support WSGI SAPI, WSGI more simple.

-----=D3=CA=BC=FE=D4=AD=BC=FE-----
=B7=A2=BC=FE=C8=CB: FGM at GMail [mailto:fgmarand@gmail.com]=20
=B7=A2=CB=CD=CA=B1=BC=E4: 2010=C4=EA9=D4=C213=C8=D5 20:25
=CA=D5=BC=FE=C8=CB: internals@lists.php.net
=D6=F7=CC=E2: [PHP-DEV] WSGI-like SAPI for PHP ?

Hello,

Having to do some work in Python recently, I had to dig into WSGI and =
found
that its model, much similar to what JSGI, PSGI, Rack do, seemed likely =
to
bring a potentially high performance improvement on my usual (Drupal)
environment. This also happened to match a remark done by Rasmus during =
his
presentation in late August at Drupalcon CPH, in which he advised us to
evolve Drupal towards a model with a long-term application process - PHP =
or
not, apparently not in his idea (C ?) - to avoid the massive amount of =
time
and effort currently spent on our per-page bootstrapping process, and =
return
PHP userland code to the more "templating" parts of the CMS.

However, after digging around on the list archives and elswhere, I could
find no trace of a discussion about an approach like this one. CGI/FCGI
sure, FPM sure, but nothing like WSGI. The closest approximation appears =
to
be the WPHP package, which does indeed embrace PHP within actual WSGI, =
but
does so at the cost of a fork/exec per hit, definitely the opposite of =
the
goal being looked for.

Has there ever been such a discussion, if only to dismiss the prospect =
as
incompatible with PHP/ZE ? Any pointers to more information would be
appreciated.

Frederic G. MARAND