Added by Andries Seutens, last edited by Karol Babioch on Mar 04, 2008  (view change)

Labels

 
(None)

Zend Framework: Zend_Service_Youtube Component Proposal

Proposed Component Name Zend_Service_Youtube
Developer Notes http://framework.zend.com/wiki/display/ZFDEV/Zend_Service_Youtube
Proposers Andries Seutens
Darby Felton, Zend liaison
Revision 1.0 - 31 January 2007: Added proposal draft (wiki revision: 9)

Table of Contents

1. Overview

Zend_Service_Youtube will offer a lightweight wrapper for using the Youtube APIs. It will allow you to easily integrate online videos from YouTube into your application.

2. References

3. Component Requirements, Constraints, and Acceptance Criteria

  • Implements all available YouTube API calls with consistent naming conventions.
  • Returns server responses as lightweight data objects.

4. Dependencies on Other Framework Components

  • Zend_Service_Rest
  • Zend_Service_Exception
  • Zend_Exception

5. Theory of Operation

Returns server responses as lightweight data objects.

6. Milestones / Tasks

  • Milestone 1: write proposal
  • Milestone 2: Class development
  • Milestone 3: Unit tests and debugging
  • Milestone 4: Documentation

7. Class Index

  • Zend_Service_Youtube
  • Zend_Service_Youtube_Exception
  • Zend_Service_Youtube_Result
  • Zend_Service_Youtube_Resultset

8. Use Cases

retrieve a YouTube user's public profile

retrieve YouTube's featured video's

For more possible queries, please see the class skeletons (Zend_Service_Youtube)

9. Class Skeletons

:%s/Youtube/YouTube/g

Also,

Otherwise, looks good!

Hello Matthew! I am not sure that I understand what you mean? Do you mind explaining this further?

Please correct me if I'm wrong, but I believe that Matthew means that:

  • the class names should be YouTube instead of Youtube (with a capital "T"), and
  • the _result() and _resultSet() methods may be better named _getResult() and _getResultSet(), respectively.

The listByRelated() and listByCategory() methods do not seem to have corresponding API functions in the documentation. Are these functions really available, and the documentation is just not here?

This proposed component will be superseded by the Zend_Gdata component because Google has acquired YouTube since the proposal was initially written.

Ryan Boyd has informed us that he plans to add YouTube support to the Zend_Gdata component.

See http://code.google.com/apis/