On 2005-12-12, Stephen Howard <[EMAIL PROTECTED]> wrote:
>
>>So, essentially, CA does the following upon being used:
>>1) Load all the plugins requested. Each plugin will register as being
>>used for a specific purpose (which could be "I add methods").
>>2) Verify that all required steps (such as dispatching) have a plugin
>>loaded or load the default one.
>>
> This sounds a lot like what I concluded when developing
> Application::Pipeline and WWW::Pipeline
I was thinking the same thing. I would suggest anyone interesting in
further exploring this line of thinking take a hard look at those
modules.
While I believe Stephen designed them well, note how long they've been
released and the relatively small amount of developer energy around.
My own sense that they define an academic extreme, while
CGI::Application hits a sweet spot in the amount of functionality it
provides versus abstracts.
Mark
--
http://mark.stosberg.com/
---------------------------------------------------------------------
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]
