On 3/7/07, Matthew Ratzloff <[EMAIL PROTECTED]> wrote:
Hi Bill, > I've updated the proposal page started by Gavin and Andries with yet > another proposed solution, "Solution E". I populated the class > skeletons to illustrate this solution. I would prefer Solution E (of > course :-). > > http://framework.zend.com/wiki/x/j1 So if you want to have multiple registries in one application (for different areas of control), you need to extend Zend_Registry. Well... it's an edge case, so I can live with that.
In the wiki it reads: Redesign Registry methods to store the singleton object as a static variable in the Zend/Registry.php class. Allow app to specify which class to use for the singleton, to allow subclassing. The way I look at it you don't have to extend Zend_Registry to use multiple instances. All it says is that if you want the ZF to use your own registry you can tell it to do so. I still like Zend_Debug (at the least, I don't feel it belongs in
Zend_Log, since the concept behind it is different). Just because there would only be one method now doesn't mean there wouldn't be any in the future. For example, I can see two methods already--dump() as it exists now, and dump() as it exists in your proposal. Other than that, Solution E looks good. The bucket class is dead. :-) -Matt
-- best regards, André Hoffmann
