Re: Pear Configuration

Hi, yavor shahpasov schrieb: > Here are a few options. > a) Each PEAR class has it's own config file (i.e. PEAR.ini) and it reads it > on start, use PEAR::Config to write read well, the big disadvantage is that reading config files is slower but checking class variables. Usually I preferr class variables and derived classes > b) All classes have one config file namely PEAR.ini with different sections See above. This is not always neccessary. > for each class/package > c) Use php.ini + > *) make shell scripts / web interface for configuring PEAR > *) Pear should provide methods to register an option getParam/setParam > methods > *) Configuration should be loaded/save with constructors/destructors I buy all of this, just one has to start working on it. Ulf