Re: LDAP class final question
| From: | Tomas V.V.Cox | Date: | Tue, 15 Jan 2002 00:32:14 +0000 |
| Subject: | Re: LDAP class final question | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-3933@lists.php.net to get a copy of this message | ||
Ludovico Magnocavallo wrote:
>
> My LDAP class is ready to be committed and I received my CVS account. Only
> thing is, I'm a bit puzzled as to where I should put it: I have two classes
> that extend DB_result and DB_common, and to be useful they need to be in the
> same directory as the other DB drivers, to be found by DB::connect()
>
> You suggested putting it in the PEAR hierarchy as NET_LDAP, but this will
> require the user to manually copy it to the DB/ directory to be able to use
> it.
>
> What do you suggest? Do you think the class should be put somewhere outside
> the DB package as an add-on, or inside it as a regular driver?
My bet is for making your class as a package it self. The you could be
able to mantain it the way you want. Then at install time your package
could be placed in the directory you need.
Please read more about what PEAR packages are at:
http://cvs.php.net/cvs.php/pearweb/doc/pear_package_manager.txt
Perhaps a better name for your package to match the filesystem structure
<-> class name mapping, could be DB_ldap (under the pear/ CVS module).
So people could be able to use: $ldap = DB::connect('ldap://...');
without any problem.
Good enough?
Tomas V.V.Cox