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-webserver-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).
Uwe
-----
Uwe Schindler
theta...@php.net - http://www.php.net
NSAPI SAPI developer
Bremen, Germany
> -----Original Message-----
> From: Anatol Belski [mailto:anatol....@belski.net]
> Sent: Monday, February 02, 2015 8:45 PM
> To: Andrey Andreev
> Cc: Nikita Popov; Anatol Belski; PHP internals
> Subject: Re: [PHP-DEV] [RFC][VOTE] Removal of dead or not yet PHP7 ported
> SAPIs and extensions
>
> On Mon, February 2, 2015 20:30, Andrey Andreev wrote:
> > Oh, forgot one thing ...
> >
> >
> > Mcrypt might be dead, but removing it would be a huge BC break. There
> > was some talk of binding mcrypt_*() functions to ext/openssl - I'd suggest
> > that instead of removal.
> >
> that sounds plausible, but the same one could say about mapping to be
> removed regex to pcre. If anything of that is going to be happening, so I
> would welcome another RFC and implementation.
>
> Regards
>
> Anatol
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
