Re: phpng: Refactored PHP Engine with Big Performance Improvement

From: Date: Wed, 07 May 2014 07:21:43 +0000
Subject: Re: phpng: Refactored PHP Engine with Big Performance Improvement
References: 1 2 3 4 5 6 7 8  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hi Zeev,

On Wed, May 7, 2014 08:36, Zeev Suraski wrote:
>> On 7 במאי 2014, at 09:13, Sebastian Bergmann <[email protected]> wrote:
>>
>>
>>
>> Playing devil's advocate: does anyone really need SAPIs other than
>> FastCGI, CLI, and embed? And if so: do we care enough to burden
>> ourselves with their maintenance?
>>
>
> I think you just called me "the devil" ;)
>
>
> Seriously, I can't think of any *real* reason of why anybody would
> need something other than these SAPIs in 2014 (other than FUD). Things like
> ISAPI and other more esoteric SAPIs are no brainers, and
> while mod_php may be a bit more of a leap of faith, it doesn't truly brings
> any tangible benefits over FastCGI (none that can't be relatively easily
> replicated in userland anyway, eg htscanner).
>
> I'd support it.
>
There's an RFC about it https://wiki.php.net/rfc/removal_of_dead_sapis
.
It came into being while working on the int64 branch, but now becomes more
relevant with phpng. The simple idea is first to check all those, if it
turns out those SAPIs will be supported by the authors, or at least
there's a minority using them, it might make sense to port them.
Implementing that RFC were a clean and predictable way to go IMHO.

Regards

Anatol



Thread (123 messages)

« previous php.internals (#74001) next »