<ac:macro ac:name="info"><ac:parameter ac:name="title">New Proposal Template</ac:parameter><ac:rich-text-body>
<p>This page has been created from a template that uses "zones." To proceed:</p>

<ol>
<li>Edit the page</li>
<li>Replace sample content within each zone-data tag with your own content</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for community review, move this page to the <ac:link><ri:page ri:content-title="Ready for Review" /></ac:link> section on the edit page.</li>
</ol>

<ac:macro ac:name="note"><ac:parameter ac:name="title">No placeholders allowed!</ac:parameter><ac:rich-text-body>
<p>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.</p></ac:rich-text-body></ac:macro></ac:rich-text-body></ac:macro>

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

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

Zend Framework: Zend_Registry_Namespace Component Proposal

Table of Contents

1. Overview

As Zend_Registry could be quite helpful in some situations, lack of namespaces prevents its use in third-party modules, because the risks of collision. Based on the Zend_Session_Namespace component, Zend_Registry_Namespace would allow developers to use (and lock if needed) a specific namespace in the registry to store his module's related data.

2. References

• Zend_Registry
• Zend_Session
• Namespace concept

3. Component Requirements, Constraints, and Acceptance Criteria

• This component will offer namespaces handling to Zend_Registry
• This component will provide read/write locking mechanism at namespace scale
• This component will not allow subclassing. (i.e. when reviewed, we expect to see "final" keyword in code)

4. Dependencies on Other Framework Components

• Zend_Registry

5. Theory of Operation

Usage of Zend_Registry_Namespace will be similar to Zend_Session_Namespace, since the challenges are quite the same.

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_Registry_Namespace

8. Use Cases

Main use case is

9. Class Skeletons