Hi David --
> I think we're stuck with CGI::Application:
I don't think the module name should change, but there is a larger
architecture at work here, and I am all for naming it and promoting it.
CGI-App (the module) is only one part of that architecture -- maybe a
central part, but only one part.
Let me say one thing about my own experience talking to people about the
module: I'm getting a little tired of explaining to people "...don't
let the 'CGI' in 'CGI-App' fool you -- it is not necessarily CGI-based."
It does seem like some antiquated compatibility layer, if you only hear
the name.
I have it in mind to create a new CPAN module -- a Bundle which loads
CGI-App and all the other popular modules. This bundle would also
contain some infrastructure which implements popular best practices --
for instance, harness scripts to build up project scaffolding at the
start.
BTW, I'm involved in a project called "Matchstick" (a spin off of the
Krang CMS project) which covers some of these goals. It would make much
sense to integrate that into this.
http://sourceforge.net/projects/matchstick/
That being said, in an effort to come up with a better name, I propose
we assemble a master list of names and then vote them "off the island"
until we have a winner. Anyone want to assemble a master list to start?
TTYL,
-Jesse-
--
Jesse Erlbaum
The Erlbaum Group
suppressed
Phone: 212-684-6161
Fax: 212-684-6226
---------------------------------------------------------------------
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.