From: Graham B. <gb...@po...> - 2000-10-18 09:44:56
|
On Wed, Oct 18, 2000 at 10:12:04AM +0100, John Berthels wrote: > As regular readers of this list are probably aware, I favour putting code > which may be of use to many/some applications into this (or another) API > (preferably in a way which doesn't incur bloat for the common case if > possible). > > This probably brings us back to the 'what is the best way to extend > Net::LDAP' issue. Should we implement this as a subclass of Net::LDAP to > avoid bloating the core API? The problem with this is that you either create many sub-classes, which means any user needs to create a sub-class of those if they want to use many, or you end up with one big subclass, which will be bloated. My suggestion I posted a few days back was something like use Net::LDAP::Extn qw(my_extension); which looked for the named extension and loaded it. this would make the method my_extension avaliable on all Net::LDAP objects. > Could/should this same mechanism be used to chase continuation references? Not sure, but maybe. Graham. |