[Seaside-dev] Issue 227 in seaside: #halt should always halt

[codesite-noreply at google.com]

Issue 227: #halt should always halt
http://code.google.com/p/seaside/issues/detail?id=227

Comment #8 by jfitzell:
I don't think it's particularly surprising and fix is fairly obvious: if  
you don't
like the error handler behaviour you're going to go look at other options  
for an
error handler to use.

For me, if you set up an error handler to email you in production it's  
because you
want to know about unexpected errors the user is encountering. If, as you  
say, it's
"your problem" to have a halt in your production code, then that is by  
definition an
unexpected error and therefore something you would desperately want to know  
about if
it slipped through for some reason. Users may literally be unable to use  
your
deployed application until you fix it.

I think it's reasonable for there to be an otherwise-production-ready error  
handler
that allows halts, but I don't believe that everybody (or even most people)  
want this
behaviour (at least all of the time) in production.



-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings