Thanks to you two for those ligths.
cheers
cyrille.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi
Another problem with that approach that Threads in java generally can
not be killed (or not recommended to be killed) therefore I would
assume that Servlet Container just dumps the output to /dev/null :) in
case user is gone
Renat
On 24/09/2007, #Cyrille37# <[EMAIL PROTECTED]> wrote:
> #Cyril
The only way that the server would know that the client's connection had
been disconnected is when it tried to read or write from that connection.
Until the server tries to read or write something back to the browser your
thread will continue happily chugging along. Generally no writing happens
unt
#Cyrille37# a écrit :
Hello,
I would like to know if there is a option, in the ServletServer or in
Tapestry for managing client disconnection.
I call "client disconnection" when the client press stop or back or
... while the page is loading.
If there is no option, how should we handle the ca
Hello,
I would like to know if there is a option, in the ServletServer or in
Tapestry for managing client disconnection.
I call "client disconnection" when the client press stop or back or ...
while the page is loading.
If there is no option, how should we handle the cas ?
Thanks a lot
Cyril
