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_DeveloperGarden Component Proposal

Proposed Component Name Zend_Service_DeveloperGarden
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_DeveloperGarden
Proposers Marco Kaiser
Zend Liaison Matthew Weier O'Phinney
Revision 1.0 - May 2009: Initial Draft.
1.1 - Sep 2009: Ready for Review
1.2 - Okt 2009: Completed Code, Ready for Recommendation
1.3 - Nov 2009: Renamed, and fixed some Requirements
Released with zf-1.10.0 (wiki revision: 23)

Table of Contents

1. Overview

Zend_Service_DeveloperGarden is a component to access the open development services of the german telekom.
Its called DeveloperGarden.com

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • Developergarden.com account and specific credentials

4. Dependencies on Other Framework Components

  • Zend_Soap
  • Zend_Exception
  • Zend_Service

5. Theory of Operation

You can instanciate one of the components (SMS,VoiceCall etc) to use the requested api.

6. Milestones / Tasks

  • Milestone 1: [DONE] Finish base implementation of STS - Soap Features
  • Milestone 2: [DONE] Finish base implementation of all services
  • Milestone 3: [DONE] Finish Unit Tests
  • Milestone 4: [DONE] Build Documentation

7. Class Index

  • Zend_Service_DeveloperGarden_BaseUserService
  • Zend_Service_DeveloperGarden_ConferenceCall
  • Zend_Service_DeveloperGarden_Credential
  • Zend_Service_DeveloperGarden_Exception
  • Zend_Service_DeveloperGarden_IpLocation
  • Zend_Service_DeveloperGarden_LocalSearch
  • Zend_Service_DeveloperGarden_SecurityTokenServer
  • Zend_Service_DeveloperGarden_SecurityTokenServer_Cache
  • Zend_Service_DeveloperGarden_SendSms
  • Zend_Service_DeveloperGarden_VoiceCall
  • Zend_Service_DeveloperGarden_Client_ClientAbstract
  • Zend_Service_DeveloperGarden_Client_Exception
  • Zend_Service_DeveloperGarden_Client_Soap
  • Zend_Service_DeveloperGarden_IpLocation_IpAddress
  • Zend_Service_DeveloperGarden_LocalSearch_Exception extends Zend_Service_DeveloperGarden_Exception
  • Zend_Service_DeveloperGarden_LocalSearch_SearchParameters
  • Zend_Service_DeveloperGarden_Request_<Service>_<Request>
  • Zend_Service_DeveloperGarden_Response_<Service>_<Response>
  • Zend_Service_DeveloperGarden_Response_BaseType
  • Zend_Service_DeveloperGarden_Response_Exception
  • Zend_Service_DeveloperGarden_Response_ResponseAbstract
    ...

8. Use Cases

9. Class Skeletons

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

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

Labels:
zend_service_developergarden zend_service_developergarden Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 29, 2009

    <p>I've been looking over the zipfile, and I have one big question: why does the base Developergarden class consist of solely static methods? what is their purpose, exactly?</p>

    <p>It seems to me that this information could all be passed to the individual service constructors, which would prevent the need for having a static registry they all use – particularly when you use but a single service in the component.</p>

    <p>On other technical details:</p>
    <ul>
    <li>All constructors should accept an associative array or Zend_Config object as the sole argument. This will be more future-proof in the event new parameters need to be added (see my comment above).</li>
    <li>Consider renaming the component to Zend_Service_DeveloperGarden – the MixedCasing makes it slightly more readable.</li>
    </ul>

    <p>Overall, however, the code and structure look quite good.</p>

  2. Oct 30, 2009

    <p>Thats a good question, the first point was that i maybe implement base functionality to instanciate the subclasses out of this base class and cover individual logic per sub service there.</p>

    <p>i.e.: </p>

    <p>$service = Zend_Service_Developergarden::getSendSms($args ....);</p>

    <p>but i dropped this during the dev ... i change the class make Zend_Service_Developergarden abstract and extends from there.</p>

    <p>ie. class Zend_Service_Developergarden_SendSms extends Zend_Service_DevelopergardenAbstract<br />
    i will rename and change also the options like you sayd (Zend_Config or array)</p>

    <p>is that ok?</p>

  3. Nov 10, 2009

    <p>I attached a new snap with renamed and changed structure.<br />
    Dropped the Zend_Service_Developergarden class.</p>

  4. Nov 19, 2009

    <ac:macro ac:name="note"><ac:parameter ac:name="title">Zend Acceptance</ac:parameter><ac:rich-text-body>
    <p>This component is accepted for immediate development in the standard incubator.</p></ac:rich-text-body></ac:macro>