note
t'mo
<p>I like the idea of composing subclasses of C::A into the larger application, but I didn't see how you implemented this bit of the 'technical specification':</p>
<blockquote>"...so it's easier to just disallow the whole C::A than it is to disallow certain run-modes."</blockquote>
<p>If <code>REPORTS => reports.cgi</code> is in the navigation template on every page, then how do you prevent the user from executing that particular C::A? And I don't think that</p>
<code>
# Display some method of choosing reports, probably with some authorization
# checks in there
</code>
<p>inside <code>sub choose</code> counts; it's still disallowing a certain run-mode named "choose". :-)</p>
<p>p.s. I enjoyed and learned something from being sidetracked by http://www.mail-archive.com/cgiapp@lists.erlbaum.net/msg00849.html.</p>
<div class="pmsig"><div class="pmsig-49433">
<hr><p><i>[id://247834|...every application I have ever worked on is a glorified munger...]</p>
</div></div>
320933
321064