RE: [INTERNALS-WIN] ISAPI support, do we need it?

I'm 50/50 on this.

Certainly, there is significantly reduced future benefit to the ISAPI module.

Windows XP (32bit) doesn't have IIS 6, it has IIS 5.1 -- I'm not sure that IIS 6's FastCGI works on XP. Perhaps we should validate that before jumping too far ahead.

From *my* personal perspective, I'm more than happy to drop ISAPI into the bitbucket--but I'm not so sure who's going to be affected. I can actually think of a few people who use XP Embedded with PHP in kiosk-type apps too. If we drop ISAPI, we're EOL'ing them pretty harshly.

Even if you ignore the XP/IIS issue--does dropping ISAPI == dropping Win2k?

Not that I have any issue with that either.

Garrett

-----Original Message-----
From: Pierre Joye [mailto:[email protected]]
Sent: Wednesday, December 10, 2008 2:17 AM
To: [email protected]
Subject: [INTERNALS-WIN] ISAPI support, do we need it?

hi,

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?

Cheers,
--
Pierre

http://blog.thepimp.net | http://www.libgd.org

--
Windows Internals Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php