Skip to end of metadata
Go to start of metadata

<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 Framework: Zend_Service_MailPerformance Component Proposal

Proposed Component Name Zend_Service_MailPerformance
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_MailPerformance
Proposers Cindy Poncin
Jérémie Caulier
Stephane Roucheray
Khaled Abdi
Zend Liaison TBD
Revision 1.0 - 20 March 2009: Initial Draft. (wiki revision: 11)

Table of Contents

1. Overview

MailPerformance is an e-mail and SMS delivery solution. MPRemote provides a SOAP API to control all aspects of MailPerformance :

  • create emailing campaigns,
  • create actions over campaigns,
  • create user segments,
  • import target (email addresses) in segments,
  • validate campaigns (send mails),
  • validate actions,
  • check statistics.

Zend_Service_MailPerformance is a concrete implementation of the MailPerformance MP Remote web service.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • The component must be simple to use.
  • The component must implements all the SOAP API functions

4. Dependencies on Other Framework Components

  • Zend_Loader
  • Zend_Exception
  • SimpleXMLElement
  • DOMDocument
  • SoapClient

5. Theory of Operation

Zend_Service_MailPerformanceMPRemote is a concrete implementation of the MailPerformance MP Remote web service.

6. Milestones / Tasks

  1. Publish proposal
  2. Write implementation
  3. Write Unit Tests
  4. Arrive on proposal approvable for incubator development
  5. Commit working prototype to incubator
  6. Commit passing unit tests
  7. Write initial documentation
  8. Revise code, tests, and docs based on feedback
  9. Merge changes with trunk for core release

7. Class Index

  • Zend_Service_MailPerformance
  • Zend_Service_MailPerformance_Base
  • Zend_Service_MailPerformance_Decorator
  • Zend_Service_MailPerformance_Exception
  • Zend_Service_MailPerformance_MPRemote
  • Zend_Service_MailPerformance_Param
  • Zend_Service_MailPerformance_Param_Action
  • Zend_Service_MailPerformance_Param_Campaign
  • Zend_Service_MailPerformance_Param_Cible
  • Zend_Service_MailPerformance_Param_Segment
  • Zend_Service_MailPerformance_Param_StatCible

8. Use Cases

The initial use case is being able to manage all aspects of an emailing campain using a tool that collects the datas (email addresses). ie : any website backoffice / content management system which you need to plug this Zend Service with.

9. Class Skeletons

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

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

Labels:
proposal proposal Delete
service service Delete
mail mail Delete
email email Delete
zend_service zend_service Delete
periscope periscope Delete
campaign campaign Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jul 28, 2010

    <p>I assume this component will rely on Zend_Soap rather than the soap extension directly?</p>

    <p>And could you please provide a couple of usecases?</p>

  2. Feb 08, 2011

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