[Seaside] request termination

[Cees de Groot]

On Mon, 2004-07-26 at 22:15, Avi Bryant wrote:
> Here's something I'd like an opinion on: if the browser times out when 
> waiting for a response, or the user hits the stop button, and the 
> connection is dropped, Seaside still keeps chugging away on the 
> request.  Should we terminate the process instead?  And if so, how do 
> we get a notification from the webserver about the dropped connection 
> in a portable way?
> 
Not in a portably way, I fear. But having a sensible default number of seconds a request can chug on
before the process is killed would be nice (set the default low - like 5 seconds
- and add an override method to the component?)