in reply to Re^2: Allowing Plugins
in thread Allowing Plugins

The plugin is given a person and told that this person either gets to login, or doesn't. The plugins are designed not to need any knowledge of which queries guarantee the permission, just that this record needs it.

So, what exactly is the plugin doing again that a class doesn't?

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^4: Allowing Plugins
by norkakn (Novice) on Feb 25, 2008 at 20:34 UTC
    It is a class. I'm a bit confused (I'm pretty new to perl, hopefully plugin doesn't mean something more specific in perl) The plugins will inherit from a base plugin class and just override the methods. Is there an easier way to go through modules and see what classes have the same superclass? That'd do the trick.
[reply]
      I'm confused as to why you are thinking so hard about this. Why wouldn't a allow_login() and disallow_login() method (or whatever) all within the same class suffice? From what I'm understanding, this is a one-off product that will do the translation once and you're done.
      My criteria for good software:
      1. Does it work?
      2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
[reply]
        > From what I'm understanding, this is a one-off product that will do the translation once and you're done. Nope, the next year will see ldap schema changes, additional back ends and more services being offered.
[reply]

In Section Seekers of Perl Wisdom