Well, that's cool then! Why not simply include all this stuff with PHP rather than supporting the flawed ISAPI that it currently is packaged with?
On Thu, 21 Nov 2002, Shane Caraveo wrote: > John Coggeshall wrote: > > > Shane (and everyone else): > > > > > > > > >Why don't we move PHP into a separate executable. Design a > > >"thin" ISAPI DLL which purely passes the data which the ISAPI > > >DLL exposes between the IIS process and the PHP process (or > > >process-pool for added reliability). The resulting page is > > >processed in the application server and returned to the ISAPI > > >DLL where it is output. > > > > > > Shane and I have already been looking into a similar solution for the > > UNIX version of PHP. In fact, if you ask'd him I think he's already got > > something working in this respect using FastCGI. > > This is exactly what fastcgi does. > > > > > > > Incidently, Shane weren't you involved in the Windows port of PHP? :) > > Yes, I am to blame. > > > > > > > >I think this solution will be *way* easier than trying to fix > > >every single bug in PHP so that it is utterly thread-safe and > > >crash-free. > > > > > > That's the idea. Part of the issue is that the external libraries PHP > > uses can't be promised to be thread-safe. > > > An thus why I did the isapi fastcgi plugin. www.fastcgi.com > > Shane > > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
