Michael Peters wrote:
Mark Stosberg wrote:On 2004-08-23, Kinyon, Rob <suppressed> wrote: Thanks for the response. Your counter-points are sound. While I understand your proposal would be backwards compatible, I have concerns that it could promote what I think is poor application design-- sending un-trapped perl death messages to the user.That depends. I think sending detailed error messages to the user is bad during production but during development I think it oh so handy.
One method to send detailed messages developers, while keeping sending friendly "serious error" :-) error page in production, is was discussed before and is extracted in FAQ wiki page about error 500 apache handler:
http://twiki.med.yale.edu/twiki2/bin/view/CGIapp/ApacheError500 I know it's Apache specific, but oh so handy and easy to use.Thank you, Mark Stosberg, for the original tip. We use it and it simplifies our developer's lives greatly.
Comments and enhancements on C::A wiki pages are as always welcome.
Of course I might be wrong and this tip is not relevant here, but...
...it might be. :-)
--
Peter Masiar
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
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.