Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version. Compare with Current  |   View Page History
Under Construction
This proposal is under construction and is not ready for review.

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

Zend Framework: Zend_Acl update - Roles and Resources dynamic loading Component Proposal

Proposed Component Name Zend_Acl update - Roles and Resources dynamic loading
Developer Notes update - Roles and Resources dynamic loading
Proposers Aldemar Bernal
Revision 1.0 - 17 November 2007: Proporsal created. (wiki revision: 5)

Table of Contents

1. Overview

Zend_Acl update isn't meant to be a replacement of the current good implementation of Zend_Acl, it is just an update proporsal based on get better performance in the component in medium/large ACL implementations.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will boost performance in medium/large Acl Implementations.
  • This component will allow the component to load only the needed Roles/Resources.

4. Dependencies on Other Framework Components

  • Zend_Acl
  • Zend_Role
  • Zend_Resource
  • Zend_Acl_Exception

5. Theory of Operation

This update doesn't make any change in current Zend_Acl implementations, it includes only a new method called registerLoader in the Zend_Acl component and a new abstract class called Zend_Acl_Loader_Abstract. The main object of this new feature is to be able to load dynamically Roles and Resources using an instance of the abstract class. Here an example is given to make clearer the new functionality and its use:

At bootstrap:


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_Acl
  • Zend_Acl_Loader_Abstract

8. Use Cases


... (see good use cases book)

9. Class Skeletons


Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.