[Seaside] Handling errors - staging/production

John Toohey jt at parspro.com
Fri Jun 3 14:35:34 UTC 2011

It comes from Seaside. I use Comet in my app, so I have to use the
streaming server. Does this mean that I cannot handle errors myself,
but must have SS show the user a stacktrace, or fire the debugger in
the image>

On Fri, Jun 3, 2011 at 01:16, Philippe Marschall
<philippe.marschall at gmail.com> wrote:
> 2011/6/2 John Toohey <jt at parspro.com>:
>> 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
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside


More information about the seaside mailing list