Hi Matt, I just wanted to chime in and say that based on the described functionality, approach B seems more attractive to me. That said, I also think these ideas need further discussion and definition, possibly warranting a proposal down the line.
Keep the good ideas coming! Best regards, Darby Matthew Ratzloff wrote: > A. Zend_Config parses an array of configuration data. Zend_Config_Ini > parses Ini and Zend_Config_Xml parses XML, and both extend Zend_Config. > Zend_Config_Loader handles file loading and auto-detection and will become > the primary method of loading more than one file. And this is in a > subdirectory. > > B. Zend_Config_Array parses an array of configuration data. > Zend_Config_Ini parses Ini and Zend_Config_Xml parses XML, and both extend > Zend_Config_Array (since ultimately they are converting the specialized > format into an array). Now Zend_Config is the primary, top-level class > that everyone refers to to load more than one configuration file in the > Zend_Config_* space, which ultimatly also includes things like > Zend_Config_Yaml and others. > > Option B just seems more clean to me. > > -Matt > >
