Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74001 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 22258 invoked from network); 7 May 2014 07:21:51 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 May 2014 07:21:51 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:41905] helo=klapt.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 75/C0-17246-D0FD9635 for ; Wed, 07 May 2014 03:21:49 -0400 Received: by klapt.com (Postfix, from userid 33) id EBC3E23D6106; Wed, 7 May 2014 09:21:43 +0200 (CEST) Received: from 89.204.155.36 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Wed, 7 May 2014 09:21:43 +0200 Message-ID: <63141f7adc38b6f0d02f828d26ac170b.squirrel@webmail.klapt.com> In-Reply-To: <4339111475046055305@unknownmsgid> References: <5369CED9.5010001@php.net> <4339111475046055305@unknownmsgid> Date: Wed, 7 May 2014 09:21:43 +0200 To: "Zeev Suraski" Cc: "Sebastian Bergmann" , internals@lists.php.net User-Agent: SquirrelMail/1.5.2 [SVN] MIME-Version: 1.0 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] phpng: Refactored PHP Engine with Big Performance Improvement From: anatol.php@belski.net ("Anatol Belski") Hi Zeev, On Wed, May 7, 2014 08:36, Zeev Suraski wrote: >> On 7 במאי 2014, at 09:13, Sebastian Bergmann 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