<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</li>
<li>Remove this notice</li>
<li>Save the page</li>
<li>When you are ready for review, remove the <ac:emoticon ac:name="warning" /> Under Construction notice</li>
</ol>
</ac:rich-text-body></ac:macro>
<ac:macro ac:name="note"><ac:parameter ac:name="title">Under Construction</ac:parameter><ac:rich-text-body>
<p>This proposal is under construction and is not ready for review.</p></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[
The purpose of this class is to utilise one or more FX rate sources to perform FX translations or return spot FX rates between any two currencies. Currencies will be denoted with Country Codes compliant with ISO 4217.Zend Framework: Zend_Service_Currency Component Proposal
Proposed Component Name
Zend_Service_Currency
Developer Notes
http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Currency
Proposers
André Hoffmann
Pádraic Brady
Darby Felton, Zend liaison
Revision
1.0 - not yet: created proposal (wiki revision: 8)
Table of Contents
1. Overview
2. References
3. Component Requirements, Constraints, and Acceptance Criteria
4. Dependencies on Other Framework Components
- Zend_Service_Exception
- Zend_Service_Rest
- Zend_Locale
- Zend_Currency
- Zend_Cache
5. Theory of Operation
Based on any two compliant ISO 4217 Country Currency codes, Zend_Service_Currency would fetch the relevant exchange rate from a selected source, or range of sources, and either:
a) perform a currency translation and return the result; or
b) return the relevant exchange rate
6. Milestones / Tasks
- Milestone 1: Publish relevant design notes and background on design decisions
- Milestone 2: Write Unit Tests for Use Case #1 and check implementing code into Incubator
- Milestone 3: Write Unit Tests/Code for remaining Use Cases and check implementing code into Incubator
- Milestone 4: Write documentation sufficient for core Use Cases
- Milestone 5: Perform review and additional refactoring. Assess additional Use Cases (if any).
7. Class Index
- Zend_Service_ExchangeRates_Interface
- Zend_Service_ExchangeRates
- Zend_Service_ExchangeRates_ECB
- Zend_Service_ExchangeRates_FRB
- Zend_Service_ExchangeRates_XMethods
- Zend_Service_ExchangeRates_CountryCodes_Interface
- Zend_Service_ExchangeRates_CountryCodes_UNECE
8. Use Cases
| UC-01 |
|---|
4 Comments
comments.show.hideOct 27, 2006
Louis PERRIER
<p>i'm very interesting by this proposal.</p>
Nov 25, 2007
Eric Coleman
<p>I'll second that one.</p>
Dec 27, 2007
maxim
<p>I'm interesting too. Very useful for my purposes. </p>
Dec 27, 2007
maxim
<p>But currency list is too limited.
<a class="external-link" href="http://www.ecb.int/stats/eurofxref/eurofxref-daily.xml">http://www.ecb.int/stats/eurofxref/eurofxref-daily.xml</a></p>