Previous Next

Zend_Service_Twitter

Introduction

Zend_Service_Twitter provides a client for the » Twitter REST API. Zend_Service_Twitter allows you to query the public timeline. If you provide a username and OAuth details for Twitter, it will allow you to get and update your status, reply to friends, direct message friends, mark tweets as favorite, and much more.

Zend_Service_Twitter implements a REST service, and all methods return an instance of Zend_Rest_Client_Result.

Zend_Service_Twitter is broken up into subsections so you can easily identify which type of call is being requested.

  • account makes sure that your account credentials are valid, checks your API rate limit, and ends the current session for the authenticated user.

  • status retrieves the public and user timelines and shows, updates, destroys, and retrieves replies for the authenticated user.

  • user retrieves friends and followers for the authenticated user and returns extended information about a passed user.

  • directMessage retrieves the authenticated user's received direct messages, deletes direct messages, and sends new direct messages.

  • friendship creates and removes friendships for the authenticated user.

  • favorite lists, creates, and removes favorite tweets.

  • block blocks and unblocks users from following you.

Authentication

With the exception of fetching the public timeline, Zend_Service_Twitter requires authentication as a valid user. This is achieved using the OAuth authentication protocol. OAuth is the only supported authentication mode for Twitter as of August 2010. The OAuth implementation used by Zend_Service_Twitter is Zend_Oauth.

例1 Creating the Twitter Class

Zend_Service_Twitter must authorize itself, on behalf of a user, before use with the Twitter API (except for public timeline). This must be accomplished using OAuth since Twitter has disabled it's basic HTTP authentication as of August 2010.

There are two options to establishing authorization. The first is to implement the workflow of Zend_Oauth via Zend_Service_Twitter which proxies to an internal Zend_Oauth_Consumer object. Please refer to the Zend_Oauth documentation for a full example of this workflow - you can call all documented Zend_Oauth_Consumer methods on Zend_Service_Twitter including constructor options. You may also use Zend_Oauth directly and only pass the resulting access token into Zend_Service_Twitter. This is the normal workflow once you have established a reusable access token for a particular Twitter user. The resulting OAuth access token should be stored to a database for future use (otherwise you will need to authorize for every new instance of Zend_Service_Twitter). Bear in mind that authorization via OAuth results in your user being redirected to Twitter to give their consent to the requested authorization (this is not repeated for stored access tokens). This will require additional work (i.e. redirecting users and hosting a callback URL) over the previous HTTP authentication mechanism where a user just needed to allow applications to store their username and password.

The following example demonstrates setting up Zend_Service_Twitter which is given an already established OAuth access token. Please refer to the Zend_Oauth documentation to understand the workflow involved. The access token is a serializable object, so you may store the serialized object to a database, and unserialize it at retrieval time before passing the objects into Zend_Service_Twitter. The Zend_Oauth documentation demonstrates the workflow and objects involved.

/**
 * We assume $serializedToken is the serialized token retrieved from a database
 * or even $_SESSION (if following the simple Zend_Oauth documented example)
 */
$token = unserialize($serializedToken);

$twitter = new Zend_Service_Twitter(array(
    'username' => 'johndoe',
    'accessToken' => $token
));

// verify user's credentials with Twitter
$response = $twitter->account->verifyCredentials();

注意:

In order to authenticate with Twitter, ALL applications MUST be registered with Twitter in order to receive a Consumer Key and Consumer Secret to be used when authenticating with OAuth. This can not be reused across multiple applications - you must register each new application separately. Twitter access tokens have no expiry date, so storing them to a database is advised (they can, of course, be refreshed simply be repeating the OAuth authorization process). This can only be done while interacting with the user associated with that access token.

The previous pre-OAuth version of Zend_Service_Twitter allowed passing in a username as the first parameter rather than within an array. This is no longer supported.

Account Methods

  • verifyCredentials() tests if supplied user credentials are valid with minimal overhead.

    例2 Verifying credentials

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->account->verifyCredentials();
  • endSession() signs users out of client-facing applications.

    例3 Sessions ending

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->account->endSession();
  • rateLimitStatus() returns the remaining number of API requests available to the authenticating user before the API limit is reached for the current hour.

    例4 Rating limit status

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->account->rateLimitStatus();

Status Methods

  • publicTimeline() returns the 20 most recent statuses from non-protected users with a custom user icon. The public timeline is cached by Twitter for 60 seconds.

    例5 Retrieving public timeline

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->publicTimeline();
  • friendsTimeline() returns the 20 most recent statuses posted by the authenticating user and that user's friends.

    例6 Retrieving friends timeline

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->friendsTimeline();

    The friendsTimeline() method accepts an array of optional parameters to modify the query.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

  • userTimeline() returns the 20 most recent statuses posted from the authenticating user.

    例7 Retrieving user timeline

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->userTimeline();

    The userTimeline() method accepts an array of optional parameters to modify the query.

    • id specifies the ID or screen name of the user for whom to return the friends_timeline.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

    • count specifies the number of statuses to retrieve. May not be greater than 200.

  • show() returns a single status, specified by the id parameter below. The status' author will be returned inline.

    例8 Showing user status

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->show(1234);
  • update() updates the authenticating user's status. This method requires that you pass in the status update that you want to post to Twitter.

    例9 Updating user status

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->update('My Great Tweet');

    The update() method accepts a second additional parameter.

    • in_reply_to_status_id specifies the ID of an existing status that the status to be posted is in reply to.

  • replies() returns the 20 most recent @replies (status updates prefixed with @username) for the authenticating user.

    例10 Showing user replies

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->replies();

    The replies() method accepts an array of optional parameters to modify the query.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

    • since_id returns only statuses with an ID greater than (that is, more recent than) the specified ID.

  • destroy() destroys the status specified by the required id parameter.

    例11 Deleting user status

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->status->destroy(12345);

User Methods

  • friends()r eturns up to 100 of the authenticating user's friends who have most recently updated, each with current status inline.

    例12 Retrieving user friends

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->user->friends();

    The friends() method accepts an array of optional parameters to modify the query.

    • id specifies the ID or screen name of the user for whom to return a list of friends.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

  • followers() returns the authenticating user's followers, each with current status inline.

    例13 Retrieving user followers

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->user->followers();

    The followers() method accepts an array of optional parameters to modify the query.

    • id specifies the ID or screen name of the user for whom to return a list of followers.

    • page specifies which page you want to return.

  • show() returns extended information of a given user, specified by ID or screen name as per the required id parameter below.

    例14 Showing user informations

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->user->show('myfriend');

Direct Message Methods

  • messages() returns a list of the 20 most recent direct messages sent to the authenticating user.

    例15 Retrieving recent direct messages received

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->directMessage->messages();

    The message() method accepts an array of optional parameters to modify the query.

    • since_id returns only direct messages with an ID greater than (that is, more recent than) the specified ID.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

  • sent() returns a list of the 20 most recent direct messages sent by the authenticating user.

    例16 Retrieving recent direct messages sent

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->directMessage->sent();

    The sent() method accepts an array of optional parameters to modify the query.

    • since_id returns only direct messages with an ID greater than (that is, more recent than) the specified ID.

    • since narrows the returned results to just those statuses created after the specified date/time (up to 24 hours old).

    • page specifies which page you want to return.

  • new() sends a new direct message to the specified user from the authenticating user. Requires both the user and text parameters below.

    例17 Sending direct message

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->directMessage->new('myfriend', 'mymessage');
  • destroy() destroys the direct message specified in the required id parameter. The authenticating user must be the recipient of the specified direct message.

    例18 Deleting direct message

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->directMessage->destroy(123548);

Friendship Methods

  • create() befriends the user specified in the id parameter with the authenticating user.

    例19 Creating friend

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->friendship->create('mynewfriend');
  • destroy() discontinues friendship with the user specified in the id parameter and the authenticating user.

    例20 Deleting friend

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->friendship->destroy('myoldfriend');
  • exists() tests if a friendship exists between the user specified in the id parameter and the authenticating user.

    例21 Checking friend existence

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->friendship->exists('myfriend');

Favorite Methods

  • favorites() returns the 20 most recent favorite statuses for the authenticating user or user specified by the id parameter.

    例22 Retrieving favorites

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->favorite->favorites();

    The favorites() method accepts an array of optional parameters to modify the query.

    • id specifies the ID or screen name of the user for whom to request a list of favorite statuses.

    • page specifies which page you want to return.

  • create() favorites the status specified in the id parameter as the authenticating user.

    例23 Creating favorites

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->favorite->create(12351);
  • destroy() un-favorites the status specified in the id parameter as the authenticating user.

    例24 Deleting favorites

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->favorite->destroy(12351);

Block Methods

  • exists() checks if the authenticating user is blocking a target user and can optionally return the blocked user's object if a block does exists.

    例25 Checking if block exists

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    
    // returns true or false
    $response = $twitter->block->exists('blockeduser');
    
    // returns the blocked user's info if the user is blocked
    $response2 = $twitter->block->exists('blockeduser', true);

    The favorites() method accepts a second optional parameter.

    • returnResult specifies whether or not return the user object instead of just TRUE or FALSE.

  • create() blocks the user specified in the id parameter as the authenticating user and destroys a friendship to the blocked user if one exists. Returns the blocked user in the requested format when successful.

    例26 Blocking a user

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->block->create('usertoblock);
  • destroy() un-blocks the user specified in the id parameter for the authenticating user. Returns the un-blocked user in the requested format when successful.

    例27 Removing a block

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    $response   = $twitter->block->destroy('blockeduser');
  • blocking() returns an array of user objects that the authenticating user is blocking.

    例28 Who are you blocking

    $twitter = new Zend_Service_Twitter(array(
        'username' => 'johndoe',
        'accessToken' => $token
    ));
    
    // return the full user list from the first page
    $response = $twitter->block->blocking();
    
    // return an array of numeric user IDs from the second page
    $response2 = $twitter->block->blocking(2, true);

    The favorites() method accepts two optional parameters.

    • page specifies which page ou want to return. A single page contains 20 IDs.

    • returnUserIds specifies whether to return an array of numeric user IDs the authenticating user is blocking instead of an array of user objects.

Zend_Service_Twitter_Search

Introduction

Zend_Service_Twitter_Search provides a client for the » Twitter Search API. The Twitter Search service is use to search Twitter. Currently, it only returns data in Atom or JSON format, but a full REST service is in the future, which will support XML responses.

Twitter Trends

Returns the top ten queries that are currently trending on Twitter. The response includes the time of the request, the name of each trending topic, and the url to the Twitter Search results page for that topic. Currently the search API for trends only supports a JSON return so the function returns an array.

$twitterSearch  = new Zend_Service_Twitter_Search();
$twitterTrends  = $twitterSearch->trends();

foreach ($twitterTrends as $trend) {
    print $trend['name'] . ' - ' . $trend['url'] . PHP_EOL
}

The return array has two values in it:

  • name is the name of trend.

  • url is the URL to see the tweets for that trend.

Searching Twitter

Using the search method returns tweets that match a specific query. There are a number of » Search Operators that you can use to query with.

The search method can accept six different optional URL parameters passed in as an array:

  • lang restricts the tweets to a given language. lang must be given by an » ISO 639-1 code.

  • rpp is the number of tweets to return per page, up to a maximum of 100.

  • page specifies the page number to return, up to a maximum of roughly 1500 results (based on rpp * page).

  • since_id returns tweets with status IDs greater than the given ID.

  • show_user specifies whether to add ">user<:" to the beginning of the tweet. This is useful for readers that do not display Atom's author field. The default is "FALSE".

  • geocode returns tweets by users located within a given radius of the given latitude/longitude, where the user's location is taken from their Twitter profile. The parameter value is specified by "latitude,longitude,radius", where radius units must be specified as either "mi" (miles) or "km" (kilometers).

例29 JSON Search Example

The following code sample will return an array with the search results.

$twitterSearch  = new Zend_Service_Twitter_Search('json');
$searchResults  = $twitterSearch->search('zend', array('lang' => 'en'));

例30 ATOM Search Example

The following code sample will return a Zend_Feed_Atom object.

$twitterSearch  = new Zend_Service_Twitter_Search('atom');
$searchResults  = $twitterSearch->search('zend', array('lang' => 'en'));

Zend-specific Accessor Methods

While the Twitter Search API only specifies two methods, Zend_Service_Twitter_Search has additional methods that may be used for retrieving and modifying internal properties.

  • getResponseType() and setResponseType() allow you to retrieve and modify the response type of the search between JSON and Atom.

Previous Next
Zend Framework の紹介
概要
インストール
Zend Framework を学ぶ(主に英語)
クイックスタート(ごく一部のみ日本語)
Zend Framework & MVC Introduction
プロジェクトを作成
Create A Layout
モデルとデータベーステーブルの作成
Create A Form
おめでとう!
オートローディング(英語)
Introduction
Goals and Design
Basic Autoloader Usage
Resource Autoloading
Conclusion
プラグイン(英語)
Introduction
Using Plugins
Conclusion
Zend_Layout 入門(英語)
Introduction
Using Zend_Layout
Zend_Layout: Conclusions
Zend_View プレイスフォルダ入門(英語)
Introduction
Basic Placeholder Usage
Standard Placeholders
View Placeholders: Conclusion
Zend Form デコレータを理解して使う(ごく一部のみ日本語)
Introduction
Decorator Basics
Layering Decorators
Rendering Individual Decorators
Creating and Rendering Composite Elements
結論
Zend_Session, Zend_Auth, Zend_Acl 入門(英語)
Building Multi-User Applications With Zend Framework
Managing User Sessions In ZF
Authenticating Users in Zend Framework
Building an Authorization System in Zend Framework
Zend_Search_Lucene 入門(一部日本語)
Zend_Search_Lucene Introduction
Lucene Index Structure
インデックスのオープンと生成
索引付け
検索
サポートされるクエリー
検索結果のページ化
Zend_Paginator 入門(英語)
Introduction
Simple Examples
Pagination Control and ScrollingStyles
Putting it all Together
Zend Framework リファレンス
Zend_Acl
導入
アクセス制御の洗練
高度な使用法
Zend_Amf
導入
Zend_Amf_Server(日本語)
Zend_Application
導入
Zend_Application クイックスタート
Theory of Operation
コア機能
利用できるリソースプラグイン
Zend_Auth
導入
データベースのテーブルでの認証
ダイジェスト認証
HTTP 認証アダプタ
LDAP 認証
Open ID 認証
Zend_Barcode
導入
Barcode creation using Zend_Barcode class
Zend_Barcode Objects
Zend_Barcode Renderers
Zend_Cache
導入
キャッシュの仕組み
Zend_Cache のフロントエンド
Zend_Cache のバックエンド
The Cache Manager
Zend_Captcha
導入
Captcha の方法
CAPTCHA アダプタ
SimpleCloud API: Zend_Cloud
Document Service Introduction
Queue Service Introduction
StorageService Introduction
Zend_CodeGenerator
導入
Zend_CodeGeneratorサンプル
Zend_CodeGenerator リファレンス
Zend_Config
導入
動作原理
Zend_Config_Ini(日本語)
Zend_Config_Json
Zend_Config_Xml(日本語)
Zend_Config_Yaml
Zend_Config_Writer
Zend_Config_Writer(日本語)
Zend_Console_Getopt
導入
Getopt の規則の宣言
オプションおよび引数の取得
Zend_Console_Getopt の設定
Zend_Controller
Zend_Controller クイックスタート
Zend_Controller の基本
フロントコントローラ
リクエストオブジェクト
標準のルータ
ディスパッチャ
アクションコントローラ
アクションヘルパー
レスポンスオブジェクト
プラグイン
モジュラーディレクトリ構造の規約の使用
MVC での例外
Zend_Currency
Zend_Currency について
Using Zend_Currency
Options for currencies
What makes a currency?
Where is the currency?
How does the currency look like?
How much is my currency?
Calculating with currencies
Exchanging currencies
Additional informations on Zend_Currency
Zend_Date
導入
動作原理
基本メソッド
Zend_Date API の概要
日付の作成
日付関数全般用の定数
動作例
Zend_Db
Zend_Db_Adapter(日本語)
Zend_Db_Statement(日本語)
Zend_Db_Profiler(日本語)
Zend_Db_Select(日本語)
Zend_Db_Table(日本語)
Zend_Db_Table_Row(日本語)
Zend_Db_Table_Rowset(日本語)
導入
Zend_Db_Table_Definition(日本語)
Zend_Debug
変数の出力
Zend_Dojo
導入
Zend_Dojo_Data: dojo.data エンベロープ
Dojo ビューヘルパー
Dojoフォーム要素とデコレーター
Zend_Dojo build layer support
Zend_Dom
導入
Zend_Dom_Query(日本語)
Zend_Exception
例外の使用法
基本的な使用法
Previous Exceptions (前の例外)
Zend_Feed
導入
フィードの読み込み
ウェブページからのフィードの取得
RSS フィードの使用
Atom フィードの使用
単一の Atom エントリの処理
フィードおよびエントリの構造の変更
独自のフィードクラスおよびエントリクラス
Zend_Feed_Reader
Zend_Feed_Writer
Zend_Feed_Pubsubhubbub
Zend_File
Zend_File_Transfer(日本語)
Zend_File_Transfer 用のバリデータ
Filters for Zend_File_Transfer
Zend_Filter
導入
標準のフィルタクラス群
フィルタチェイン
フィルタの書き方
Zend_Filter_Input(日本語)
Zend_Filter_Inflector(日本語)
Zend_Form
Zend_Form(日本語)
Zend_Form クイックスタート
Zend_Form_Element を用いたフォーム要素の作成
Zend_Form によるフォームの作成
Zend_Form_Decorator による独自のフォームマークアップの作成
Zend Framework に同梱されている標準のフォーム要素
Zend Framework に同梱されている標準のデコレータ
Zend_Form の国際化
Zend_Form の高度な使用法
Zend_Gdata
導入
AuthSub による認証
Using the Book Search Data API
ClientLogin による認証
Google Calendar の使用法
Google Documents List Data API の使用法
Using Google Health
Google Spreadsheets の使用法
Google Apps Provisioning の使用法
Google Base の使用法
Picasa Web Albums の使用法
YouTube Data API の使用法
Gdata の例外処理
Zend_Http
導入
Zend_Http_Client - 高度な使用法
Zend_Http_Client - 接続アダプタ
Zend_Http_Cookie および Zend_Http_CookieJar
Zend_Http_Response(日本語)
Zend_Http_UserAgent
The UserAgent Device Interface
The UserAgent Features Adapter
The WURFL UserAgent Features Adapter
The DeviceAtlas UserAgent Features Adapter
The TeraWurfl UserAgent Features Adapter
The UserAgent Storage Interface
The Session UserAgent Storage Adapter
Zend_InfoCard
導入
Zend_Json
導入
基本的な使用法
Zend_Json の高度な使用法
XML から JSON への変換
Zend_Json_Server - JSON-RPCサーバー
Zend_Layout
導入
Zend_Layout クイックスタート
Zend_Layout の設定オプション
Zend_Layout の高度な使用法
Zend_Ldap
導入
API概要
利用シナリオ
ツール
Zend_Ldap_Nodeを使用してLDAPツリーへのオブジェクト指向アクセス
LDAPサーバから情報を取得
LDIFへ、または、からのLDAPデータシリアライズ
Zend_Loader
ファイルやクラスの動的な読み込み
The Autoloader
Resource Autoloaders
プラグインのロード
Zend_Locale
導入
Zend_Locale の使用法
正規化および地域化
日付および時刻の扱い
サポートするロケール
Zend_Log
概要
ライター
フォーマッタ
フィルタ
Using the Factory to Create a Log
Zend_Mail
導入
SMTP 経由での送信
SMTP 接続による複数のメールの送信
異なる転送手段の使用
HTML メール
ファイルの添付
受信者の追加
MIME バウンダリの制御
追加のヘッダ
文字セット
エンコーディング
SMTP 認証
セキュアな SMTP トランスポート
メールメッセージの読み込み
Zend_Markup
導入
さあ始めましょう
Zend_Markup パーサー
Zend_Markup レンダラー
Zend_Measure
導入
計測値の作成
計測値の出力
計測値の操作
計測値の型
Zend_Memory
概要
メモリマネージャ
メモリオブジェクト
Zend_Mime
Zend_Mime(日本語)
Zend_Mime_Message(日本語)
Zend_Mime_Part(日本語)
Zend_Navigation
導入
画面
Containers
Zend_Oauth
Introduction to OAuth
Zend_OpenId
導入
Zend_OpenId_Consumer の基本
Zend_OpenId_Provider(日本語)
Zend_Paginator
導入
使用法
設定
高度な使用法
Zend_Pdf
導入
PDF ドキュメントの作成および読み込み
PDF ドキュメントへの変更内容の保存
ページの操作
描画
Interactive Features
ドキュメントの情報およびメタデータ
Zend_Pdf モジュールの使用例
Zend_ProgressBar
Zend_ProgressBar(日本語)
Zend_Queue
導入
使用例
フレームワーク
アダプタ
Zend_Queueのカスタマイズ
Stomp(日本語)
Zend_Reflection
導入
Zend_Reflectionサンプル
Zend_Reflectionリファレンス
Zend_Registry
レジストリの使用法
Zend_Rest
導入
Zend_Rest_Client(日本語)
Zend_Rest_Server(日本語)
Zend_Search_Lucene
概要
インデックスの構築
インデックスの検索
クエリ言語
クエリ作成用の API
文字セット
拡張性
Java Lucene との相互運用
応用
ベストプラクティス
Zend_Serializer
導入
Zend_Serializer_Adapter
Zend_Server
導入
Zend_Server_Reflection(日本語)
Zend_Service
導入
Zend_Service_Akismet(日本語)
Zend_Service_Amazon(日本語)
Zend_Service_Amazon_Ec2(日本語)
Zend_Service_Amazon_Ec2: Instances
Zend_Service_Amazon_Ec2: Windows Instances
Zend_Service_Amazon_Ec2: Reserved Instances
Zend_Service_Amazon_Ec2: CloudWatch Monitoring
Zend_Service_Amazon_Ec2: Amazon Machine Images (AMI)
Zend_Service_Amazon_Ec2: Elastic Block Storage (EBS)
Zend_Service_Amazon_Ec2: Elastic IP Addresses
Zend_Service_Amazon_Ec2: Keypairs(日本語)
Zend_Service_Amazon_Ec2:リージョンおよび利用可能ゾーン
Zend_Service_Amazon_Ec2: Security Groups
Zend_Service_Amazon_S3
Zend_Service_Amazon_Sqs
Zend_Service_Audioscrobbler(日本語)
Zend_Service_Delicious(日本語)
Zend_Service_DeveloperGarden
Zend_Service_Ebay
Zend_Service_Ebay_Finding
Zend_Service_Flickr(日本語)
Zend_Service_LiveDocx
Zend_Service_Nirvanix(日本語)
Zend_Service_ReCaptcha(日本語)
Zend_Service_ShortUrl
Zend_Service_Simpy(日本語)
Zend_Service_SlideShare(日本語)
Zend_Service_StrikeIron(日本語)
Zend_Service_StrikeIron: バンドルされているサービス
Zend_Service_StrikeIron: 応用編
Zend_Service_Technorati(日本語)
Zend_Service_Twitter
Zend_Service_WindowsAzure
Zend_Service_WindowsAzure_Storage_Blob
Zend_Service_WindowsAzure_Diagnostics_Manager
Zend_Service_WindowsAzure_Storage_Queue
Zend_Service_WindowsAzure_Storage_Table
Zend_Service_Yahoo(日本語)
Zend_Session
導入
基本的な使用法
高度な使用法
グローバルセッションの管理
Zend_Session_SaveHandler_DbTable(日本語)
Zend_Soap
Zend_Soap_Server(日本語)
Zend_Soap_Client(日本語)
WSDLアクセッサ
自動検出
Zend_Tag
導入
Zend_Tag_Cloud
Zend_Test
導入
Zend_Test_PHPUnit(日本語)
Zend_Test_PHPUnit_Db(日本語)
Zend_Text
Zend_Text_Figlet(日本語)
Zend_Text_Table(日本語)
Zend_TimeSync
導入
Zend_TimeSync の動作
Zend_Tool
Using Zend_Tool On The Command Line
Extending Zend_Tool
Zend_Tool_Framework
導入
CLIツールの使用
アーキテクチャ
Zend_Tool_Frameworkを利用してプロバイダを作成する
出荷されたシステムプロバイダー
Extending and Configuring Zend_Tool_Framework
Zend_Tool_Project
導入
プロジェクトを作成
Zend_Tool Project Providers
Zend_Tool_Project Internals
Zend_Translate
導入
Zend_Translate のアダプタ
翻訳アダプタの使用法
ソースファイルの作成
翻訳用の追加機能
Plural notations for Translation
Zend_Uri
Zend_Uri(日本語)
Zend_Validate
導入
標準のバリデーションクラス群
バリデータチェイン
バリデータの書き方
検証メッセージ(一部日本語)
Zend_Version
Zend Framework のバージョンの取得
Zend_View
導入
コントローラスクリプト
ビュースクリプト
ビューヘルパー
Zend_View_Abstract(日本語)
Zend_Wildfire
Zend_Wildfire(日本語)
Zend_XmlRpc
導入
Zend_XmlRpc_Client
Zend_XmlRpc_Server(日本語)
ZendX_Console_Process_Unix
ZendX_Console_Process_Unix
ZendX_JQuery
Introduction
ZendX_JQuery View Helpers
ZendX_JQuery Form Elements and Decorators
Zend Framework のシステム要件
導入
Zend Framework 移行上の注意
Zend Framework 1.10(一部日本語)
Zend Framework 1.9(一部日本語)
Zend Framework 1.8(日本語)
Zend Framework 1.7(日本語)
Zend Framework 1.6(日本語)
Zend Framework 1.5(日本語)
Zend Framework 1.0(日本語)
Zend Framework 0.9(日本語)
Zend Framework 0.8(日本語)
Zend Framework 0.6(日本語)
Zend Framework PHP 標準コーディング規約
概要
PHP ファイルの書式
命名規約
コーディングスタイル
Zend Framework ドキュメント標準(一部日本語)
概要
ドキュメントファイル形式
推奨事項
Zend Framework MVC アプリケーションのために推奨されるプロジェクト構造
概要
推奨されるプロジェクト・ディレクトリ構造
モジュール構造
リライト設定ガイド
Zend Framework パフォーマンスガイド
導入
クラスの読み込み
Zend_Dbパフォーマンス
国際化(i18n)とローカライズ(l10n)
ビューのレンダリング
著作権に関する情報