Right now the site IS a collection of CGI scripts that do individual states. Sure, it works, but even using a common routine module, a change in one part of the script might need updating elsewhere. I'd rather have a system where there is one common starting point for authenication checking, cookie collection, and the like, and similar exit point for rendering and logging, as to avoid code duplication. Providing such hooks such that the CGI functions are considered plugins, as opposed to common routines being plug-ins for the CGI, can make the code more uniform, and easier to update. Using CGI::Application with a huge state machine or a node system would handle both of these isssues.
-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com
||
"You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important