New Proposal Template This page has been created from a template that uses "zones." To proceed: Edit the page Replace sample content within each zone-data tag with your own content Remove this notice Save the page When you are ready for community review, move this page to the Ready for Review section on the edit page. No placeholders allowed! Please do not create placeholders. Wait until you have sufficient content to replace all sample data in the proposal template before creating your proposal document.

<ac:macro ac:name="unmigrated-inline-wiki-markup"><ac:plain-text-body><![CDATA[

Zend Framework: Zend_Container Component Proposal

Table of Contents

1. Overview

Zend_Container is a simple dependency injection container that is intended to replace use of Zend_Registry and class-based singletons. This is a proposal for a simpler dependency injection component than Zend_Di and Zend_Context. Note that the word "component" is overloaded in this proposal. This proposal is for a Zend Framework "component" but it also uses the word "component" to refer to an object managed by Zend_Container.

2. References

• PicoContainer
• Inversion of Control Containers and the Dependency Injection pattern

3. Component Requirements, Constraints, and Acceptance Criteria

• This component will replace Zend_Registry.
• This component will use reflection.
• This component will not allow more than one instance of a given type to be registered in a given container.
• This component will not act as a factory (except for creating the single instance of a given type).
• This component will allow manual component registration or configuration-based component registration.
• This component will allow a hierarchy of containers.
• This component will allow a container to have zero or one parent container.
• This component will allow a container to have zero or more child containers.
• This component will allow a child container to access components in its parent container.
• This component will not allow a parent container to access components in its child container(s).

• Zend_Reflection
• Zend_Loader
• Zend_Config (optional)
• Zend_Exception

4. Dependencies on Other Framework Components

5. Theory of Operation

The component is instantiated with a mind-link that ...

6. Milestones / Tasks

Describe some intermediate state of this component in terms of design notes, additional material added to this page, and / code. Note any significant dependencies here, such as, "Milestone #3 can not be completed until feature Foo has been added to ZF component XYZ." Milestones will be required for acceptance of future proposals. They are not hard, and many times you will only need to think of the first three below.

• Milestone 1: design notes will be published here
• Milestone 2: Working prototype checked into the incubator supporting use cases #1, #2, ...
• Milestone 3: Working prototype checked into the incubator supporting use cases #3 and #4.
• Milestone 4: Unit tests exist, work, and are checked into SVN.
• Milestone 5: Initial documentation exists.

If a milestone is already done, begin the description with "[DONE]", like this:

• Milestone #: [DONE] Unit tests ...

7. Class Index

• Zend_Magic_Exception
• Zend_Magic (factory class)
• Zend_Magic_MindProbe
• Zend_Magic_MindProbe_Intent
• Zend_Magic_Action
• Zend_Magic_CodeGen

8. Use Cases

... (see good use cases book)

9. Class Skeletons