Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:86885
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.169 as permitted sender)
MIME-Version: 1.0
Sender: kalle.php@gmail.com
In-Reply-To: <CALW=WEAg0Tpp3bkBB4=RytrUMcBXvFUPN0XwX6FfNB3-2cJG7Q@mail.gmail.com>
References: <CALW=WEAg0Tpp3bkBB4=RytrUMcBXvFUPN0XwX6FfNB3-2cJG7Q@mail.gmail.com>
Date: Thu, 25 Jun 2015 22:53:11 +0200
Message-ID: <CAJW__o2jxxt0z2yqo7u_wtDrfXChwgUKfftMryZZ4mFN1AGRug@mail.gmail.com>
To: "S.A.N" <ua.san.alex@gmail.com>
Cc: internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] New PHP SAPI for Nginx
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

2015-06-25 22:31 GMT+02:00 S.A.N <ua.san.alex@gmail.com>:
> New versions Nginx, implement thread pools,
> http://nginx.com/blog/thread-pools-boost-performance-9x/
>
> I think this is a good opportunity to write a Nginx module (PHP SAPI)
> which is to process requests for PHP scripts in processes Nginx.
>
> Quality advantages, as compared with the FPM, no network overhead,
> less memory consumption, may be implemented mode ZTS (Zend Thread
> Safety).
>
> What do you think about this?
> Thank.

If there is someone willing to implement this (and maintain it), I
don't see any reason for why this could not be accepted into PHP. I
would expect such, if implemented by someone, to first be available in
7.1.0, although we could do exceptions like we did for FPM which came
in 5.3.3 or something, although that was before tuning to our RFC
process and such.

-- 
regards,

Kalle Sommer Nielsen
kalle@php.net