[Seaside] request termination

Brian Brown rbb at techgame.net
Tue Jul 27 17:22:56 CEST 2004


On Jul 26, 2004, at 2:15 PM, 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?
>

This would be phenomenal! That is another issue I've had problems with 
in the past in OWF (Other Web Frameworks) The stop button doesn't mean 
a whole lot to them if you stop a big request in the middle.


> At least in Squeak, terminating the process does make sure to run all 
> the #ensure: blocks, and I expect/hope the same would be true in other 
> dialects as well.  So as long as people are careful, it shouldn't do 
> *too* much damage to kill the process.  It's also unlikely that the 
> callback processing is what would take too long and timeout (barring 
> an inifinite loop) - usually it would be the render phase getting 
> terminated, which should be pretty harmless.
>

And we care about other dialects why? (Just kidding!)

> A
>
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside



More information about the Seaside mailing list