0.1 - 29 January 2008: Started proposal process
0.2 - 24 Febuary 2008: Proposal ready for review
0.3 - 11 June 2008: Added type casting (wiki revision: 26)
3. Component Requirements, Constraints, and Acceptance Criteria
It will read XML or php context files.
It will not read ini files.
It will provide a static class for getting objects.
It will provide methods for creating components from code.
It will provide interface for reading variables from config files
4. Dependencies on Other Framework Components
Zend_Exception
Zend_Loader
5. Theory of Operation
Configure the objects and their relations/dependencies of an application's context in a simple way (php or xml files) and load them easily.
For dynamic component creation and loading there will be a small interface.
<p>Oops, I didn't see that. Thanks for telling.<br />
There are lots of DI implementations. Zend_Di is like PicoContainer's and Zend_Context is like Spring Framework's. I will complete the proposal and than watch, how Zend_Di's proposal will go (and use Zend_Context on my projects, as I do now)</p>
<p>I updated Use Case #5 with a Zend_Config example. I didn't rely on just Zend_Config, because it can not understand attributes of xml nodes. I tend to like xmls for config/context definitions (maybe this comes from using Spring and Eclipse <ac:emoticon ac:name="smile" />)</p>
<p>Is this proposal ready for review? If so, please move it to the correct section and announce the move on the mailing list.<br />
Also, there is a proposal that add attribute support to Zend_Config_Xml that is currently under consideration.</p>
<p>Yes, it is <ac:emoticon ac:name="smile" />. I moved it to the ready for review section.<br />
I wrote an email to the core list, but I'm not sure if it arrived.</p>
<p>Zend_Config_Xml Attribute Support looks promising and if it is accepted, than I can consider moving onto it.</p>
<p>Archiving this proposal, feel free to recover it when you want to work on it again. For more details see <a href="http://framework.zend.com/wiki/display/ZFDEV/Archiving+of+abandoned+proposals+(Feb+5+2011)">this email</a>.</p>
6 Comments
comments.show.hideJan 30, 2008
Pádraic Brady
<p>You might want to review current proposals:
<a class="external-link" href="http://framework.zend.com/wiki/display/ZFPROP/Zend_Di+-+Dependency+Injection+Container">http://framework.zend.com/wiki/display/ZFPROP/Zend_Di+-+Dependency+Injection+Container</a></p>
<p>At a minimum I would strongly prefer DI to rely on using Zend_Config as input.</p>
Jan 30, 2008
Peter Kovacs
<p>Oops, I didn't see that. Thanks for telling.<br />
There are lots of DI implementations. Zend_Di is like PicoContainer's and Zend_Context is like Spring Framework's. I will complete the proposal and than watch, how Zend_Di's proposal will go (and use Zend_Context on my projects, as I do now)</p>
<p>I updated Use Case #5 with a Zend_Config example. I didn't rely on just Zend_Config, because it can not understand attributes of xml nodes. I tend to like xmls for config/context definitions (maybe this comes from using Spring and Eclipse <ac:emoticon ac:name="smile" />)</p>
May 13, 2008
Wil Sinclair
<p>Is this proposal ready for review? If so, please move it to the correct section and announce the move on the mailing list.<br />
Also, there is a proposal that add attribute support to Zend_Config_Xml that is currently under consideration.</p>
<p>Thanks.<br />
,Wil</p>
Jun 12, 2008
Peter Kovacs
<p>Yes, it is <ac:emoticon ac:name="smile" />. I moved it to the ready for review section.<br />
I wrote an email to the core list, but I'm not sure if it arrived.</p>
<p>Zend_Config_Xml Attribute Support looks promising and if it is accepted, than I can consider moving onto it.</p>
Sep 03, 2008
Peter Kovacs
<p>I see that, ZF 1.6 has attribute support now. Because of arrays in parameters:</p>
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
<constructor>
<arg>PDO_Pgsql</arg>
<arg>
<array>
<elem key="host">db.example.com</elem>
<elem key="port" type="int">1234</elem>
<elem key="username">dbuser</elem>
<elem key="password" value="secret"/>
<elem key="dbname" value="db"/>
</array>
</arg>
</constructor>
]]></ac:plain-text-body></ac:macro>
<ac:macro ac:name="code"><ac:plain-text-body><![CDATA[
"constructor"=>array(
array("value"=>"PDO_Pgsql")
,array(
"value"=>array(
array("key"=>"host","value"=>"db.example.com")
,array("key"=>"port","type"=>"int","value"=>"1234")
,array("key"=>"username","value"=>"dbuser")
,array("key"=>"password","value"=>"secret")
,array("key"=>"dbname","value"=>"db")
)
)
)
]]></ac:plain-text-body></ac:macro>
<p>I will have to rethink the structure to rely fully (only) on Zend_Config.</p>
Feb 07, 2011
Dolf Schimmel (Freeaqingme)
<p>Archiving this proposal, feel free to recover it when you want to work on it again. For more details see <a href="http://framework.zend.com/wiki/display/ZFDEV/Archiving+of+abandoned+proposals+(Feb+5+2011)">this email</a>.</p>