Top listings

Zend_Uri is a component that aids in manipulating and validating Uniform Resource Identifiers (URIs). Zend_Uri exists primarily to service other components such as Zend_Http_Client but is also useful as a standalone utility.
URIs always begin with a scheme, followed by a colon. The construction of the many different schemes varies significantly. The Zend_Uri class provides a factory that returns a subclass of itself which specializes in each scheme. The subclass will be named Zend_Uri_<scheme>, where <scheme> is the scheme lowercased with the first letter capitalized. An exception to this rule is HTTPS, which is also handled by Zend_Uri_Http.

With web applications written using PHP, a session represents a logical, one-to-one connection between server-side, persistent state data and a particular user agent client (e.g. web browser). Zend_Session helps manage and preserve session data, a logical complement of cookie data, across multiple page requests by the same client. Unlike cookie data, session data is not stored on the client side, and it is only shared with the client when server-side source code makes the data available via a response to a request from the client. For the purposes of this component and documentation, session data refers to the server-side data managed by Zend_Session.

Zend_Server_Reflection provides a standard mechanism for performing function and class introspection for use with server classes. It is based on PHP 5's Reflection API, and extends it to provide methods for retrieving parameter and return value types and descriptions, a full list of function and method prototypes (i.e., all possible valid calling combinations), and function/method descriptions.
Typically, this functionality will only be used by developers of server classes for the framework.

Zend_Service_Amazon is a simple API for using Amazon web services. Zend_Service_Amazon has two APIs: a more traditional one that follows Amazon's own API, and a simpler "Query API" for constructing even complex search queries easily.
Zend_Service_Amazon enables developers to retrieve information appearing throughout Amazon.com web sites directly through the Amazon Web Services API. Examples include: Store item information, such as images, descriptions, pricing, and more; Customer and editorial reviews; Similar products and accessories; Amazon.com offers; ListMania lists.

Zend_Service_Flickr is a simple API for using the Flickr REST Web Service.

Zend_Service_Akismet provides a client for the Akismet API. The Akismet service is used to determine if incoming data is potentially spam; it also exposes methods for submitting data as known spam or as false positives (ham). Originally intended to help categorize and identify spam for Wordpress, it can be used for any type of data.

Akismet requires an API key for usage. You may get one for signing up for a WordPress.com account. You do not need to activate a blog; simply acquiring the account will provide you with the API key.

Additionally, Akismet requires that all requests contain a URL to the resource for which data is being filtered, and, because of Akismet's origins in WordPress, this resource is called the blog url. This value should be passed as the second argument to the constructor, but may be reset at any time using the setBlogUrl() accessor, or overridden by specifying a 'blog' key in the various method calls.

Zend_Service_Yahoo is a simple API for using many of the Yahoo! REST APIs. Zend_Service_Yahoo allows you to search Yahoo! Web search, Yahoo! News, Yahoo! Local, Yahoo! Images.

Zend_View is a class for working with the "view" portion of the model-view-controller pattern. That is, it exists to help keep the view script separate from the model and controller scripts. It provides a system of helpers, output filters, and variable escaping.
Zend_View is template system agnostic; you may use PHP as your template language, or create instances of other template systems and manipulate them within your view script.
Essentially, using Zend_View happens in two major steps: 1. Your controller script creates an instance of Zend_View and assigns variables to that instance. 2. The controller tells the Zend_View to render a particular view, thereby handing control over the view script, which generates the view output.

In Part 8 of this series, we added Yahoo!, Amazon, and Flickr results to the Chomp application. Now we're going to improve performance by loading only the data the user requests, when the user requests it.

This tutorial is for developers who want to learn about creating a simple mashup, a Web application that uses information from different sources. It uses the Zend Framework's Zend_Services component and the principle of Representational State Transfer (REST) to demonstrate how to seamlessly include information to extra resources related to our feeds.
Using the examples of Amazon Web Services (AWS), Flickr Services, and Yahoo! Search Web services, this tutorial teaches you how to apply the PHP Zend Framework to quickly search those sites for relevant information. You will integrate this functionality into the Chomp feed reader developed in the previous parts of this series.