[Catalyst] Re: Error handling strategy wrt /end

[apv]

Forwarding to a true static error page (outside of Catalyst) might 
really be the right way to go. Your view is as likely to be broken as 
any other part of the app. Bomb-proofing assumes worst case. Even if 
your controller is working, you can't be sure your template engine is. 
And even fallback with ErrorDocument statements to the same pages.

-apv

On Thursday, January 26, 2006, at 08:49  PM, Phil Mitchell wrote:

> Thanks for these samples! You're both catching /end errors in /end -- 
> which I think is the right thing to do, now that I see it. The only 
> thing I may do differently is forward to a static error page, but 
> forwarding to a stable, simple error template is probably fine, too.
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 716 bytes
Desc: not available
Url : http://lists.rawmode.org/pipermail/catalyst/attachments/20060126/f4307047/attachment.bin