[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cgiapp] Re: RFC: Standard config interface for CGI::Application


On 2005-12-20, Ron Savage <suppressed> wrote:
> Let's make it a short slope!
>
> I propose adding 2:
>
> o log_config
> o session_config
>
> How many web apps do without both of these?
>
> All others, repeat all others, are optional.

It seems like you might be confusing standard config names with standard
APIs. It seems like you are thinking of

 # logging configs inside!
 $self->config('log_config');

At the moment, I'm not interesting doing anything with sessions in the
core, because there seems to be a lot less need for for a standard API
there. How many  other plugins want to use a session object? Maybe just
the Auth plugins that I can think of. 

As far I'm concerned, ::Plugin::Session and CGI::Session can be the
defacto API to follow, and session plugins can follow suit. 

Logging on the other hand is a lot like "warn" and "die"-- nearly every
plugin could make use of them.

But I should I stop now. I'm tired and grumpy.

    Mark

-- 
http://mark.stosberg.com/ 


---------------------------------------------------------------------
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.