Hi Andi and all others, I am sorry but I think keeping four classes in one file is even worse than the current Zend class. Sounds a bit like premature optimization. Many framework beginners already have problems to understand the purpose of the Zend class. I am afraid that with your approach confusion might even grow bigger.
One reason people almost mention when they are explaining why they favor the Zend Framework over other frameworks is this: "because I only need to load and use the stuff I really want to use". If someone does not want to use the Zend_Registry why forcing him to load it on each request? I think, Framework beginners should be told to build proper bootstrap files to load and setup all the framework stuff they need on each request. IMHO this is rather a task for documentation, tutorials and sample applications than for file organization. Someone who is really trying to tweak the performance as far as that loading one or two files really counts, might probably be a little annoyed to have to load Zend_Framework or Zend_Registry classes on each request if they don't need them. These guys will tweak the framework any way to fit their needs. I still think that dividing the current Zend class into Zend_Loader, Zend_Registry, etc. classes which are located in a file each, is the better approach. And I would also favor the simple renaming of the Zend class to a single Zend_Core class over your approach of having four classes in one file. Jm2c. Thanks and Best Regards, Ralf
