I prefer Apache::ASP + HTML::FillInForm.

You get:

• Automatic Session handling (via MLDBM::Sync by default)
• Script_On(Start|End|Parse|Flush) events
• Session_On(Start|End) events
• Application_On(Start|End) events
• Emailed error reports (emails server errors right to your inbox - highly configurable)
• Simple upload handling ($Request->Upload(...))
• Friendly interface to the Apache server API
  • $Server->RegisterCleanup( sub {...} )
  • $Response->Redirect(...)
  • $Response->End
• print $str actually works
• Familiar <% %> and <%= %> syntax

I have used Apache::ASP on a variety of projects, both low- and high-traffic and I have to say it performs well enough. Energy Works and ETundra both run Apache::ASP. I have also written some large scale in-house applications on Apache::ASP that I cannot link to.

Having extended the base Apache::ASP code in several different ways (altered XMLSubs behavior, db-persisted sessions, MVC-enhanced URI mapping, etc) I can attest to the quality of the underlying code in Apache::ASP as well - it's easy to override what you need to override without running into encapsulation issues.

I give Josh Chamas (maintainer of Apache::ASP) an A+ on his work. Check out the Apache::ASP homepage at http://www.apache-asp.org/ for more information.