Re: extending Auth DB container

On Wednesday 20 March 2002 18:50, Ken Chew wrote: > I am a new user of pear and wanted to extend the DB container > class for Auth to add some of my own function for the user auth. > > But I note that this part > 269 function _factory($driver, $options = "") > 270 { > 271 $storage_path = "Auth/Container/" . $driver . ".php"; > 272 $storage_class = "Auth_Container_" . $driver; > 273 > 274 require_once $storage_path; > 275 > 276 return new $storage_class($options); > 277 } > > default to looking for the driver in the pear directory. > > Now, I do not have write access to this directory (actually do not > want to write to there). If I want to put my own driver file > somewhere, what should? > > I'm pretty new at objects and such, so would appreciate if you > could provide some details. May be it would be good to add the feature that the $driver can also be a complete path to an external class, so people can extend the Auth-containers as they might want to implement some proprietary functionality inside!? (remember Martin, i suggested that once too) I think it makes sense implemeting something like this then the Auth instance would be created somehoe like this: new Auth( '/my/class/file.php' , $options ); or however the setting up is supposed to be, the parameters are the important thing in this example -- Wolfram ... translating template engine .... http://sf.net/projects/simpletpl