I need to ask a really stupid question here since I dropped back in after the plugin discussion was had. What is the difference between a CGI::Application plugin and an imported/inherited class? From reading the documentation and looking at some of these modules it seems to be a matter of semantics and little else. (I probably just squarely inserted my foot in my mouth.) Perhaps my background in MT is what is tripping me up because a plugin actively hooks into that system via specific API calls rather then the app hooking into it.
For the most part you are correct. Plugins will usually just export specific methods into the application's namespace to be used by that application. But, there is some work going on to create a hook-based API for registering and running code at specified points in the application lifetime. While this is open to people using C::A normally, this is not it's main intent. It is to provided an API for plugins to register code that will later be run.
So for now, a 'C::A plugin' is a simple semantic sugar for a 'collection of imported methods' it is not intended to remain that way. As we see the power of plugins more and more, I expect C::A to implement a more exanped API just for plugins. I think we have a good jumping off point.
-- Michael Peters Developer Plus Three, LP
--------------------------------------------------------------------- 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]
