On 12/20/05, Mark Stosberg <[EMAIL PROTECTED]> wrote:
> On 2005-12-20, Michael Peters <[EMAIL PROTECTED]> wrote:
> >
> > I'm actually leaning toward Graham's idea here that it just be in the
> > plugins. I
> > like the API but I'm not sure it's something that should be in the core. I
> > know
> > configuration is something pretty basic that every framework should have,
> > but I
> > don't see C::A as a framework... more as a framework for building
> > frameworks.
>
> In my v2 RFC I proposed a very minimum of code in the core:
>
> sub config { return undef }
>
> And that's just a convenience for plugin authors so they don't have to
> check if the 'config' method exists, they can directly check
>
> $self->config('key_i_want');
I want to create a standard logging API that plugins and users can use
as well (with plugins that support Log::Dispatch, Log::Log4perl and
simple print to STDERR plugins). Should we add stubs for those
methods into the core as well?
Although 'config' is a pretty common requirement, I think it is a
slippery slope adding a stub for it into the core.
That having been said, I do believe a common configuration API is
necesary that other modules/plugins can depend on.
Cheers,
Cees
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
