On Wed, Dec 21, 2005 at 01:56:24PM -0500, Clayton Scott wrote:
> Hi Gang,
>
> I am concerned about the base of these things (logining,configuration)
> being implimented in a namespace called "CGI::Application::Plugin."
> Plugin is a pretty random grab bag of tricks.
I agree. I think the modules that define the standard API for config'ing,
logging
and session handling deserve their own name space.
> Does anyone else see value in renaming certain "Pluggable plugins"
> like we're discussing here with a more meaningful namesapce like
> Aspect or Concern?
I don't like these two names myself. I thought of "API" which is clear
it defines an API. Maybe then:
CGI::Application::API::Config;
But the existing config plugins keep their name (let's not rename /everything/!)
CGI::Application::Plugin::ConfigAuto;
CGI::Application::Plugin::Config::Simple;
etc.
However, they would start being implemented with API::Config.
On the other hand, Cees is making a case for a general plugin loading
solution, which /would/ be appropriate to give a name like
CGI::Application::Plugin
It looks like the "config()" conversation has turned into
"CGI::Application, the Next Generation"....
Mark
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
