Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81648 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40488 invoked from network); 2 Feb 2015 20:33:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Feb 2015 20:33:20 -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:58663] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 76/23-25089-E0FDFC45 for ; Mon, 02 Feb 2015 15:33:19 -0500 Received: by h1123647.serverkompetenz.net (Postfix, from userid 33) id 1276123D6002; Mon, 2 Feb 2015 21:33:12 +0100 (CET) Received: from 87.159.48.115 (SquirrelMail authenticated user anatol@belski.net) by webmail.klapt.com with HTTP; Mon, 2 Feb 2015 21:33:12 +0100 Message-ID: <47e6c87257cf0b54059054ea748a2d6b.squirrel@webmail.klapt.com> In-Reply-To: <01bf01d03f25$adcf53d0$096dfb70$@php.net> References: <2ebcb8f91e4185726e4bf49d5e675c2a.squirrel@webmail.klapt.com> <01bf01d03f25$adcf53d0$096dfb70$@php.net> Date: Mon, 2 Feb 2015 21:33:12 +0100 To: "Uwe Schindler" Cc: "'PHP internals'" 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] [RFC][VOTE] Removal of dead or not yet PHP7 ported SAPIs and extensions From: anatol.php@belski.net ("Anatol Belski") Hi Uwe, On Mon, February 2, 2015 21:20, Uwe Schindler wrote: > Hi, > > > I gave my votes (where I can talk about). I am still maintaining the > NSAPI > SAPI. It does not meant that its dead if no commits were made. NSAPI > upstream API just did not change since years, so why change a running > system? > > The current version of this SAPI (5.6) runs perfectly with MediaWiki and > several CMS systems on latest Oracle iPlanet server in production. The > information about NSAPI you gave ("The developers of iPlanet @Oracle > wrote back, that they're not intended to support this SAPI starting from > PHP7 > onwards.") is not applicable, because people from Sun/Oracle never > provided any support or this extension - you should have asked the > maintainer (me). Oracle just recommends fcgi, because it might be more > stable if you use non-threadsafe extensions, but otherwise the server is > perfectly stable and very fast. Oracle employees only helped with one > patch, otherwise it was mostly (re-)written by me. In addition, the server > works perfectly fine on Ubuntu 14.04, so it will also run on Debian. It > can be downloaded with Oracle OTN license, header files are included. You > can compile PHP 5.6 with it as documented: > http://www.oracle.com/technetwork/java/webtier/downloads/iplanet-webserve > r-525365.html > > If there are changes needed in the SAPI for PHP 7, I can take care, I > just have not looked into it. It should not be a problem for me to update > it, unless significant changes in the PHP API occurred since my last > commit (yes, I am a bit inactive, but still following the development). > yeah, I saw your reply previously that it's worky with PHP5, however couldn't test (whereby it turned out iPlanet is available not only for SunOS). But then I had the reply from the @Oracle devs and thought it's were cleared. Please check what happened to Apache SAPI (just to estimate the efforts), there's quite some change after the phpng and TLS merge. If you think it'd be acceptable for you to port and maintain in the ufture, so lets restart the vote right now and exclude sapi/nsapi. Thanks. Anatol.