Hello PHP-Developers I have an idea!
I recently went through the pain of creating an ISAPI DLL for IIS and what I found was that IIS was *incredibly* sensitive to things "going wrong" in the DLL with the result that the IIS process would hang and the whole damn machine would need a "reboot" on a regular basis. So, I went back to the drawing board for version 2 of my DLL and I designed an architecture whereby the DLL would be the "thinnest" I could possibly make it, and the "guts" would be in a separate application server. I accomplished communication between the DLL and the application server via named pipes, which are very fast and efficient on Win NT and above servers. This works fine and I've never had an IIS crash since. 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. Then if PHP crashes for whatever reason (i.e. database-client library bug), a) it won't take down IIS and b) it can simply be restarted and continue serving requests. A bit like the way it runs on UNIX really with Apache's process-pool architecture. 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. It would also scale more nicely because you could run multiple PHP binaries across different machines if you are doing very intensive PHP stuff. I think this might solve the pain of trying to run PHP on IIS in a non-CGI environment with a relatively trivial piece of code. 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. Additionally if there is a problem with my idea, I'd love to hear from you all. Nick. On Thu, 21 Nov 2002, Maxim Maletsky wrote: > > Derick Rethans <[EMAIL PROTECTED]> wrote... : > > > On Thu, 21 Nov 2002, John Coggeshall wrote: > > > > Again, what about IIS, etc? > > > > Who cares? :) It really would be much better if some person who thinks > > IIS rulez fixes the ISAPI module. If that doesn't work correctly nobody > > should use it at all. > > Never used IIS in my entire life, but I would be scared shall PHP start loosing > its IIS support letting .NET and Java more space on Win32 systems. > > I am sure there are cases when IIS is prefered to Apache on MS servers > and when MS is prefered for certain production architectures and these > architectures are prefer by certain brains. > > Don't ask me why - I hate that myself, but we should not ignore if want > to be competitive. > > > -- > Maxim Maletsky > [EMAIL PROTECTED] > > > > -- > 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
