Mark Stosberg wrote:
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.
While some part of me certainly wouldn't mind having more people using
my code, Mark is right ... my order of tuits has been back ordered for
months, and there are a number of updates that I either haven't
implemented or haven't uploaded to CPAN. Mark has been kind enough on
more than one occasion to make good suggestions along the same lines.
But my point of posting was more a prior art kind of thing. That _if_
people are wondering what a sparse-skeleton/all-plug in architecture
looks like, I've made one, and use it in production on a daily basis. I
apologize if it merely looked like I was taking a chance for self-promotion.
-Stephen
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
---------------------------------------------------------------------
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]
