Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49617
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.160.42 cause and error)
Message-ID: <4C8E3FFB.9030105@lerdorf.com>
Date: Mon, 13 Sep 2010 08:15:07 -0700
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: FGM at GMail <fgmarand@gmail.com>
CC: internals@lists.php.net
References: <AANLkTimWkEEUoCvEGbb_a3zu5exiQa5p1YA9vrEPNPr6@mail.gmail.com>
In-Reply-To: <AANLkTimWkEEUoCvEGbb_a3zu5exiQa5p1YA9vrEPNPr6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] WSGI-like SAPI for PHP ?
From: rasmus@lerdorf.com (Rasmus Lerdorf)

On 9/13/10 5:24 AM, FGM at GMail wrote:
> 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.

I think that was some creative listening on your part.  I talked about
moving the rendering engine to C, not about any sort of persistent
application process.

-Rasmus