"Gaetan Lehmann" <[EMAIL PROTECTED]> writes: >>> + darcsweb should stop darcs when a request to a page is cancelled: a >>> darcs diff for example can take a lot of time and doesn't need to run if >>> the user cancel is request.
>> I don't know how the CGI interface is supposed to let the >> application know >> about this... so I'm open to suggestions =) > I don't know how, but the jobs I launch in a cgi are killed if I > cancel the request before the end of the job. It was a problem for > me, but in that case, it would be useful :-) >From http://www.modpython.org/pipermail/mod_python/2001-April/011772.html | Third, if the browser cancelled the request the only way to find out | is to try to send the reply and get some sort of bad status. Imagine | a script that does a set of time-consuming database queries to | create the output. it would be useful to test whether the request | was cancelled after each query by attempting to send something back | (a space character perhaps) to see whether the socket is still open | before doing the rest of the queries. Don't know if that helps (or even if it is correct). -k -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ darcs-users mailing list [email protected] http://www.abridgegame.org/mailman/listinfo/darcs-users
