[Seaside] Handling errors - staging/production

[John Toohey]

This I don't understand, as all that has happened is that my app has
thrown an error, and I have just emailed the error report, and now
want to continue. I haven't actually stopped sending what ever was in
progress when the error occurred. Why was the response committed so
quickly?

On Fri, Jun 3, 2011 at 01:15, Philippe Marschall
<philippe.marschall at gmail.com> wrote:
> 2011/6/2 John Toohey <jt at parspro.com>:
>> I see the last exception is thrown because I'm using a
>> WAStreamResponse, and its already committed. At this stage I would
>> just like to redirect to an error page, and have the user log back in.
>> Is there any way to exit the chain, and perform a redirect?
>
> You can't. Once the response it committed the bytes are on the client
> (or at least on their way). You can try to send a JavaScript that does
> a redirect but that may not work. If you're uncool with this behavior
> don't use streaming.
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
~JT