Re^4: Allowing Plugins

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.

Comment on Re^4: Allowing Plugins

Replies are listed 'Best First'.
Re^5: Allowing Plugins by dragonchild (Archbishop) on Feb 25, 2008 at 21:33 UTC
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: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^6: Allowing Plugins by norkakn (Novice) on Feb 25, 2008 at 22:43 UTC
> 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]
Re^7: Allowing Plugins by dragonchild (Archbishop) on Feb 26, 2008 at 17:01 UTC
So why aren't you just authenticating and authorizing against the LDAP backend that's containing all this information? Why the synchronization process? My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]