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. Incidently, Shane weren't you involved in the Windows port of PHP? :) >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. >If anyone wants to take this on I can give source code to my >DLL and application server to give you a kickstart in the >right direction. I'm CC'ing Shane on this... -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
