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, except that I didn't do step 2.
Phases in the pipeline that didn't have methods registered simply didn't
run. This didn't really present an issue for me because a) there are so
few phases in a WWW::Pipeline that they're hard to overlook, and b) A
few plugins provided the base methods for most of those phases. It
seems to me that perhaps CGI::Application should consider loading
'standard' plugins for steps where a plugin hasn't already been
assigned, rather than falling back on hard coded default methods.
-Stephen
---------------------------------------------------------------------
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]
