It's the same difference. Either way, a custom registry is required for that use case.
-Matt > 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. > > 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.
