RE: [INTERNALS-WIN] ISAPI support, do we need it?
[email protected] ("Andi Gutmans")
| Newsgroups | php.internals.win |
|---|---|
| Message-ID | <[email protected]> |
> -----Original Message----- > From: Pierre Joye [mailto:[email protected]] > Sent: Wednesday, December 10, 2008 7:47 AM > To: Steph Fox > Cc: [email protected] > Subject: Re: [INTERNALS-WIN] ISAPI support, do we need it? > > On Wed, Dec 10, 2008 at 4:30 PM, Steph Fox <[email protected]> wrote: > > Hi Pierre, > > > >> ISAPI has been the sapi of choices for the last decade on windows with > >> IIS or PWS. Now that FastCGI support is available for IIS6/7 on all > >> supported windows versions (supported by MSFT or php.net) including > >> XP, Vista, 2k, 2k3 and 2k8 (x86 or x64), I would like to stop to > >> support the ISAPI interface. We can do it in php 5.3.x as it is an > >> important enough update both from a features point of view and for the > >> Windows platforms. > >> > >> > >> Any objection? Comments? > > > > It's way late to talk about dropping support for any SAPI in PHP 5.3.* IMHO. > > Being in alpha stage and approximately 6 to 8 months away from a > stable releases, I do not think it is too late. > > > If you're planning to do this (and I assume you're saying it on M$ advice) > > You are assuming too much :) This proposal is based on a fact: nobody > gives a damned to the ISAPI. How do you know this for a fact? I actually bump into people who are using ISAPI and some are quite happy. I do try and convince them to move to FastCGI but I think you are underestimating how many people use the ISAPI version. I also think there's another Web Server which also is based on ISAPI interfaces but forgot which one but I think it's a source and not binary compatibility. My suggestion is to keep the ISAPI sources in the sapi/ tree, not build the binary for the ISAPI extension for PHP 5.3.0 and have a README.ISAPI in the binary package explaining why it's not included, recommending to download MS FastCGI and if they want to send us feedback they should email [email protected]. This way we can check whether it's truly sought after or not. Based on that we can course correct if needed. My 2 cents. Andi