> It simplifies and standardizes the way a plugin can be built for
> CGI::Application, and it works completely outside of the
> CGI::Application codebase (ie no patches necesary). It avoids the
> annoyances of building a big inheritance tree for the plugins you want
> to use by copying a given set of methods into the callers namespace. No
> exporting or name space munging needs to be done by the plugin modules,
> as this is done automatically.
Cees,
Thanks for contributing this. I'm not sure I "get it", though. It looks
like you have re-invented a way for some methods in a plugin module to
be exported, while others are not.
Without this framework, CGI::App::Session worked fine and was as easy to
use as I hoped a plug-in would be. What's the additional value that this
framework provides over the techniques used for that?
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.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]
