Handling errors - staging/production

> 2011/6/2 John Toohey <[hidden email]>:
>> I have that with the Seaside class, but am not sure what to do beyond
>> that (if anything). Should I send a redirect to an error page or
>> handle the exception some other way. On my production servers, I often
>> see socket timeout errors etc., and would like to just have these
>> emailed/logged to disk, and not have the debugger come up in the
>> image.
>
> Do you get them from within Seaside or from within Comanche?
>
> Cheers
> Philippe
> _______________________________________________
> seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>

> 2011/6/2 John Toohey <[hidden email]>:
>> 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
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>