<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_Service_Amazon_Abstract is an abstract class for Amazon Web Service that will standardize the key handling across the services..![]()
This proposal has been archived, and its various improvements are now addressed with issue ZF-5791. Zend Framework: Zend_Service_Amazon_Abstract Component Proposal
Proposed Component Name
Zend_Service_Amazon_Abstract
Developer Notes
http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Amazon_Abstract
Proposers
Jon Whitcraft
Zend Liaison
TBD
Revision
1.0 - 15 Feburary 2009: Initial Draft. (wiki revision: 5)
Table of Contents
1. Overview
2. References
3. Component Requirements, Constraints, and Acceptance Criteria
4. Dependencies on Other Framework Components
5. Theory of Operation
This will provide the methods for extending future amamzon web service classes to be based from.
6. Milestones / Tasks
- Milestone 1: Working prototype checked into the incubator supporting use cases
- Milestone 2: Unit tests exist, work, and are checked into SVN.
7. Class Index
- Zend_Service_Amazon_Abstract
8. Use Cases
| UC-01 |
|---|
class Zend_Service_Amazon_Sqs extends Zend_Service_Amazon_Abstract {
}
1 Comment
comments.show.hideFeb 15, 2009
Justin Plock
<p>It's a good idea, but I just wanted to point out that I also proposed Zend_Queue which would include an adapter for using Amazon's SQS service. The Zend_Queue code in the standard incubator actually already works with SQS and a database backend. Someone could probably easily support MemcacheQ (<a class="external-link" href="http://memcachedb.org/memcacheq/">http://memcachedb.org/memcacheq/</a>) as well. So...I'm not sure if we should keep the queuing code separated out or try to combine the Amazon Services together.</p>