note
jdrago_999
I prefer Apache::ASP + HTML::FillInForm.
<br><br>
You get:
<ul>
<li>Automatic Session handling (via MLDBM::Sync by default)</li>
<li><code>Script_On(Start|End|Parse|Flush)</code> events</li>
<li><code>Session_On(Start|End)</code> events</li>
<li><code>Application_On(Start|End)</code> events</li>
<li>Emailed error reports (emails server errors right to your inbox - highly configurable)</li>
<li>Simple upload handling (<code>$Request->Upload(...)</code>)</li>
<li>Friendly interface to the Apache server API
<ul>
<li><code>$Server->RegisterCleanup( sub {...} )</code></li>
<li><code>$Response->Redirect(...)</code></li>
<li><code>$Response->End</code></li>
</ul>
</li>
<li><code>print $str</code> actually works</li>
<li>Familiar <% %> and <%= %> syntax</li>
</ul>
<br><br>
I have used Apache::ASP on a variety of projects, both low- and high-traffic and I have to say it performs well enough. <a href="http://www.energyworks123.com/">Energy Works</a> and <a href="http://www.etundra.com/">ETundra</a> both run Apache::ASP. I have also written some large scale in-house applications on Apache::ASP that I cannot link to.
<br><br>
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.
<br><br>
I give Josh Chamas (maintainer of Apache::ASP) an A+ on his work. Check out the Apache::ASP homepage at <a href="http://www.apache-asp.org/">http://www.apache-asp.org/</a> for more information.
542332
542332