Re: [INTERNALS-WIN] ISAPI -> FastCGI

On Wed, Dec 31, 2008 at 1:10 PM, Richard Quadling
<[email protected]> wrote:
> 2008/12/31 Pierre Joye <[email protected]>:
>> ISAPI should be kept, however we may disable it before 5.3.0-final but
>> leave the sources in place for 3rd parties (there is a discussion on
>> this list about that). FastCGI is the supported SAPI for IIS these
>> days (by php or MSFT), as it works way better than ISAPI.
>
> EEK! I use ISAPI and not on IIS. I use Sambar Server (which is defunct
> and doesn't support FastCGI - just plain CGI).

PHP 5.3.0 and 6.0.0 are our next major releases. It makes no sense to
bloat them and make our work harder only to support dead web servers
(dead now already :).

> Why can't it remain. It works for me very well. Admittedly I'm only
> serving about 100 users 24/7 (utilises with COM for Crystal Reports,
> MS Word/Excel file production, PDF production, etc.).

You can always stay with 5.2.x (which will be maintained after 5.3.0
final, for at least a year or so), then migrate to 5.3/IIS when you
are ready.

> Once of the benefits of using ISAPI over CGI was the persistence of
> database connections. Is there any advantage to this now? Does FastCGI
> this in some way?

Yes, per fcgi process.

Cheers,
-- 
Pierre

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