Skip to end of metadata
Go to start of metadata

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

This proposal has been archived, and its various improvements are now addressed with issue ZF-5791.

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

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

Zend_Service_Amazon_Abstract is an abstract class for Amazon Web Service that will standardize the key handling across the services..

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • This component will be an abstract class.
  • This component will provide a standard starting base for all amamzon aws classes
  • This component will extend Zend_Service_Abstract

4. Dependencies on Other Framework Components

  • Zend_Service_Abstract
  • Zend_Service_Amamzon_Exception

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 {
}

9. Class Skeletons

]]></ac:plain-text-body></ac:macro>

]]></ac:plain-text-body></ac:macro>

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Feb 15, 2009

    <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>