Re: CVS update: php3

> i believe many people would like their script to get "killed" when the connection is > aborted without changing their > (working-) code (just install a new apache, change one ini setting), on the other hand we > should not change the "standard" > behaviour in the current php3 code - so why not leave it up the the webmaster/developer how the > script handle connection > abort stuff..... Well, the behaviour was pretty much undefined before. It did actually work in some cases, but it wasn't reliable. So for some people we are changing the way it works, for others we are not. The big benefit here is that it is now defined and cosistent. I'll stick in a .ini directive and an access function to help people control it, and will leave the default to be that scripts get aborted on a user abort. > (BTW: do you think we can implement the same thing for the NT cgi version (i m unlucky enough > to have NT customers....;-()) No idea. This is outside my scope. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net