At 17:55 21/08/2002, Joseph Tate wrote: >o Rewrite the ISAPI IIS interface. "Gasp". From the ground up, or find >some other way to fix bug #15333. The work arounds listed in the bug report >are not acceptable in production systems, just as temporary stop-gap methods >for developing new applications until a true fix is found.
Well, here's one easy to remove :) There's nothing wrong with the ISAPI interface. Nothing that warrants rewriting it, anyway. The bug in question is most probably not related to ISAPI at all; Any corruption or thread safety bug in any part of PHP can cause it. My bet is a thread safety issue in one of the database modules, or based on the report and some personal experience, the session module under Windows. Also note that I fixed a few serious threading issues last week, so multithreaded stability should be better, even though I don't think the bugs I fixed could lead to hard crashes as described in the bug report. >o Fix register_shutdown_function to work as it did with 4.1, or add a >seperate function to add this functionality. And then get it to work on >windows. See bug #15209. I don't think that this kind of features should be in the roadmap for 5. I don't have anything against them, and I won't mind finding them in 5, but it's really not a pre-requisite. I think that at this point we should switch from wish-list mode, to a down-to-earth realistic mode. That is, not put everything that we want to see in the roadmap, but only things which are either pre-requisites or things we know with a great deal of certainty. I did take a look at the bug report and noticed I even analyzed it once... Basically, we can implement a new set of functions in the Apache module. We can definitely not switch back to the old behavior because it would lead to a serious inconsistency across servers. Zeev -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
