Guys, I was following this discussion for long time but now I'm confused
a little. As far as I remember original idea of C::A::Plugin, every
plugin should have structure like this:
============= quote from C::A::Plugin documentation ===============
package CGI::Application::Plugin::MyPlugin
use base 'CGI::Application::Plugin';
sub method_name : CGIAppPluginMethod {
my $self = shift;
# This method is exported to the plugged-in module
}
sub this_method_is_not_exported {}
===================================================================
but all plugins currently developed use different approach using
Exporter, like this:
============= quote from C::A::Plugin::DBH code ===================
package CGI::Application::Plugin::DBH;
use strict;
use vars qw($VERSION @ISA @EXPORT_OK);
require Exporter;
@ISA = qw(Exporter);
@EXPORT_OK = qw(
dbh
dbh_config
);
sub dbh {
my $self = shift;
...........
}
===================================================================
Did I miss something? I mean it seems like C::A::Plugin is not
obligatory itself for any of this plugin. Is the initial idea of
C::A::Plugin deprecated now?
I was going to implement C::A::Plugin::Log but now I'm little confused
which way to go.
> We are now close to this vision with the plugins now available. There's
>
> cfg()
> dbh()
> validate_rm()
> session()
>
> Mark
WBR, Vitaliy
---------------------------------------------------------------------
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]
