Rasmus Lerdorf wrote:
> What does it do?  Using connection_status() in a script that doesn't
> ignore user aborts is pretty useless. 

Regardless of whether I use ignore(0) or ignore(1), the script keeps going
after the user has hit stop. The apache error-log is then full of:

(32)Broken pipe: core_output_filter: writing data to the network

> The script will abort on the print
> and never get to the connection_status() line so your code doesn't
> actually make any sense. 

OK, that's good to know too :-)
 
> And, beyond that, all bets are off for
> Apache-2.0.x.  No real extensive testing has been done on that platform
> which is why we don't suggest running it in production because stuff like
> this is likely to be broken even if you got your code right.

Fair enough - this isn't production as such - I thought it might be worth
asking. What are the plans, if any,  regarding apache 2.0.x and php? 

For my purposes, I would be perfectly happy if my php script would stop
running once the client has disconnected. 

/Per

-- 
Per Jessen, Zurich
http://timian.jessen.ch - an analog report formatter using XSLT.
http://www.dansk.org - for alle danskere i udlandet!


-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to