what happens when client press "Stop"?

[Chameleon]

I have a BIG php output and I start to transmit after client's request.

What happen on server when client press "Stop"?

PHP continues to send data? Where? Until the end?

[ZeldorBlat]

Re: what happens when client press "Stop&quot ;?


Chameleon wrote:

I have a BIG php output and I start to transmit after client's request.
>
What happen on server when client press "Stop"?
>
PHP continues to send data? Where? Until the end?

It depends. By default, when the connection is aborted (i.e. when the
user presses the "stop" button in their browser) the script stops
executing. This behavior can be changed with the ignore_user_abo rt
directive in php.ini or with the ignore_user_abo rt() function. In this
case, the script will run to completion and you can detect the client
disconnect using connection_abor ted().

More details can be found here:

<http://www.php.net/manual/en/features.connec tion-handling.php>

[Sandman]

Re: what happens when client press &quot;Stop&quot ;?

In article <1157487807.151 365.18690@h48g2 000cwc.googlegr oups.com>,
"ZeldorBlat " <zeldorblat@gma il.comwrote:

Chameleon wrote:

I have a BIG php output and I start to transmit after client's request.

What happen on server when client press "Stop"?

PHP continues to send data? Where? Until the end?

>
It depends. By default, when the connection is aborted (i.e. when the
user presses the "stop" button in their browser) the script stops
executing. This behavior can be changed with the ignore_user_abo rt
directive in php.ini or with the ignore_user_abo rt() function. In this
case, the script will run to completion and you can detect the client
disconnect using connection_abor ted().
>
More details can be found here:
>
<http://www.php.net/manual/en/features.connec tion-handling.php>

Yeah, but you can only perform server-side actions, no output will be
sent to the browser after the user clicks stop. Just worth mentioning.


--
Sandman[.net]