It was the logical place for us, since these scripts are created by our
CGI::Application configuration environment, attaching the error handler here
was easy. In addition, it is the very top level, so no matter what dies, or
where, your eval{ } will catch it.
We looked at Error.pm a while back, but decided to keep it simple and follow
the error throwing system of HTML::Template and CGI::Application, using
die( ) and text messages, which seems to work.
-- Cory
> -----Original Message-----
> From: Christopher Hicks [mailto:suppressed
> Sent: Monday, February 03, 2003 11:22 AM
> To: CGI::Application mailing list; Cory Trese
> Subject: RE: [cgiapp] Customized Error Screens
>
>
> On Mon, 3 Feb 2003, Cory Trese wrote:
>
> > I have attached a proof-of-concept, which shows the basic idea. It
> > contains specific code for our session, configuration, security, and
> > instance script generation stuff, but the idea is relatively clear.
>
> I hadn't thought of using the cgi script to be the upper catch, but that
> makes good sense. Now to make it work with Error.pm....
>
> --
> </chris>
>
> "Never offend people with style when you can offend them with substance."
> - Sam Brown
>
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.