compared with
Version 3 by Thomas Weidner
on Apr 05, 2010 09:22.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (4)

View Page History

{zone-data:requirements}
Most requirements take the form of "foo will do ...." or "foo will not support ...", although different words and sentence structure might be used. Adding functionality to your proposal is requirements creep (bad), unless listed below. Discuss major changes with your team first, and then open a "feature improvement" issue against this component.

* This component *will* correctly reads a developers mind for intent and generate the right configuration file.
* The generated config file *will not* support XML, but will provide an extension point in the API.
* This component *will* use no more memory than twice the size of all data it contains.
* This component *will* include a factory method.
* This component *will not* allow subclassing. (i.e. when reviewed, we expect to see "final" keyword in code)
* This component *will* only generate data exports strictly complying with RFC 12345.
* This component *will* validate input data against formats supported by ZF component Foo.
* This component *will not* save any data using Zend_Cache or the filesystem. All transient data *will be* saved using Zend_Session.
* This component *will* return hash values for given input
* This component *will* support multiple adapters like Zend_Filter_Encrypt
{zone-data}


{zone-data:operation}
The component is instantiated with a mind-link that ...
Zend_Filter_Hash provides a filter which can be used within other components which allow the usage of filters. It provides adapters for several available extensions and methods.
{zone-data}