Last week we discussed the new Zend Framework extension and gave you a look inside its functionality. This week we take off where we ended last week, and delve into remote objects and Zend_Amf!
First, get Zend_Amf up and running by downloading Zend Framework version 1.7 or later from the Zend Framework website. When you land on the Zend Framework download page, scroll to the bottom: You should see a table listing the currently available versions. As of this writing, Zend Framework version 1.7 is only available as a preview release. Extract the downloaded archive to a convenient location, like C:\ZF on Windows. Make a note of this location, because you'll copy files from that location in a moment.
Next, set up your web server's directory structure for Zend_Amf. In your server's web root folder, create a new directory called include. Beneath include, create another directory called services. The services directory houses the classes that Zend_Amf uses. The services folder and structure for a default WampServer installation are shown in Figure 4.



Figure 4. The services directory structure for a default WampServer installation
Notice two files in the services folder: Contact.php and ContactService.php. Create those files now, and leave them empty for the moment: You'll add the code in a few minutes. Next, navigate to the directory above the web root of your web server-that is, the directory that contains the www, htdocs, or public_html folder. If you're using WampServer on Windows, the path to this folder is C:\wamp. From the folder to which you extracted the Zend Framework (C:\ZF in this example), copy the library folder and paste it here. You should now have the Zend Framework components under the library/Zend folder. The correct folder structure is shown in Figure 5.



Figure 5. The library/Zend folder structure
Now that your directory structure is in place, create a gateway file that will serve as an endpoint for Flex client connections. In your web root directory, create a new PHP file called index.php, then open it in your PHP editor. This file will instantiate a Zend_Amf server and expose your methods to the Flex clients. Paste the code shown in Listing 4 into the index.php file.
Listing 4. The PHP code to create a Zend_Amf endpoint
if(set_include_path('c:\wamp\library') === false){
 die('Include path failed');
require_once 'Zend/Amf/Server.php'; 
require_once 'include/services/ContactService.php'; 
// Instantiate server 
$server = new Zend_Amf_Server(); 
// Handle request 
$response = $server->handle();
echo $response;
The first statement, an if test, sets the include path to the Zend Framework installation. If the include cannot be completed, the script fails. Next, the Zend_Amf server is brought in along with your service class file. The server is instantiated, and the setClass method is used to specify a remote service-in this case, ContactService. The $server->setClassMap() line is very important when using custom classes: This property is used to map classes between ActionScript and PHP. When this value is properly set, you can dictate the type of objects you send and receive in your Flex application. The fist value, ContactVO, is the name of the ActionScript class; the second value, Contact, is the name of the corresponding PHP class.
The next line, $server->setProduction(false), should be used with caution. Setting this property to False increases the verbosity of the output from Zend_Amf; this is helpful for debugging but can be dangerous in production, so be sure to switch it to True in a production environment. The $response variable holds the output of the Zend_Amf server as it handles requests from clients. Finally, the response is echoed back to the client. You now need to set up the classes for use with Zend_Amf. From the webRoot/include/services directory, open the ContactService.php file you created a moment ago. Paste the code shown in Listing 5 into the empty file.
Listing 5. The PHP remote methods are defined within the ContactService class
include 'Contact.php';
class ContactService {
* get contacts 
* @return array
	function getContacts() {
		$dbh = mysql_connect('localhost', 'root');
		$listAll = 'SELECT * FROM contacts.contacts';
		$result = mysql_query($listAll, $dbh);
		$contactsArray = array();
		while ($row = mysql_fetch_array($result)) {
			$contact = new Contact();
			$contact->name = $row['name'];
			$contact->email = $row['email'];
			$contact->phone = $row['phone'];
			array_push($contactsArray, $contact);
		return $contactsArray;
* save 
* @param  Contact $contact 
* @return null 
  	function saveContact(Contact $contact) {
  		$name = $contact->name;
  		$email = $contact->email;
  		$phone = $contact->phone;
  		$dbh = mysql_connect('localhost', 'root');
  		$insert = "INSERT INTO contacts.contacts (id, name, email, phone) VALUES (NULL, '$name', '$email', '$phone')";
		$doInsert = mysql_query($insert, $dbh);

Similar to the XMLService.php file you created in part 2, the getContacts() method of this PHP script queries the database for all the contacts in the contacts table. However, instead of assembling an XML string, the getContacts() function loops through the result, building new Contact objects from each returned row. Then, each new contact is pushed into an array. The array of contact objects is returned to the client. The saveContact() method will accept a new Contact object from the Flex client and insert it into the database. Note Again, make sure the credentials in the mysql_connect() function match your MySQL login credentials.
To create objects of the type Contact, you must define the contact object. To do so, open the Conatct.php file from the webRoot/include/services directory. Paste the code shown in Listing 6 into the empty file.
Listing 6. The Contact object defined in PHP
class Contact {
	public $id = 0;
	public $name = "";
	public $email = "";
	public $phone = "";
The properties of the Contact class are simple and probably familiar. Each contact has an integer for an ID and a few string properties. Save your files, and pull up your web browser. Navigate to the root address of your web server-in most cases, http://localhost. If the PHP files and directories are configured properly, you will either see text similar to "Zend_Amf Server" or be prompted to download a file of type application/x-amf. Figure 6 shows this behavior in Mozilla Firefox.



Figure 6. The server sends an AMF message when the gateway file is requested
Now that your Zend_Amf gateway and server are up and running, you're ready to create a Flex client to take advantage of them.
Creating the Zend_Amf Flex client
Note You can skip this section by importing the Flex Project archive provided in the zip archive. The Zend_Amf Flex Client source archive resides in attachedArchive/ProjectArchives/
Extract the XMLandPHP project archive to a convenient directory. In Flex Builder, click File > Import > Flex Project. In the dialog box that appears, choose the archive, and then click Finish. The ZendAMF project will be added to your Flex Builder workspace.
Now that you have set up the necessary PHP code, create the Flex client to make requests and display the output. Go back to the main MXML file of the XMLandPHP project you created in the last section.
To switch the application from using HTTPService to RemoteObject, you must make a few code modifications. First, change creationComplete="xmlService.send()" in line 1 to read creationComplete="roContactService.getContacts()". This change makes the application call the RemoteObject you're about to create rather the HTTPService you used in the last section.
Next, scroll down to the <mx:HTTPService> tag and highlight the entire component-that is, everything between the <mx:HTTPService> tags and the tags themselves. Right-click the selected code, and then choose Source > Toggle block comment. The code will be commented out. Below the commented code, add an <mx:RemoteObject> tag. The code for the new RemoteObject is shown in Listing 7.
Listing 7. The RemoteObject created in MXML
<mx:RemoteObject endpoint="http://localhost/index.php" 
id="roContactService" destination="zend" source="ContactService" 
		<mx:method name="getContacts" result="handleContacts(event)" fault="handleFault(event)"/>
		<mx:method name="saveContact" result="handleSave(event)" 
The RemoteObject specifies the endpoint, a unique ID, a source, and a destination. The endpoint is the URL to your Zend_Amf gateway file, the destination is an arbitrary name, and the source is the name of the remote class you're calling. There is also a handler for a fault during the communication-a function called handleFault(). Make sure your source property matches the name of the PHP file containing your methods.
Within the RemoteObject, you also declare the methods to be accessed from the client. The first method, getContacts, returns an array of Contact objects, as you'll recall from the PHP class file. The second method, saveContact(), will be called to insert a new record into the database. Make sure these method names are exactly the same as those declared in the PHP file containing your methods.
Next, change the ActionScript code to tie everything together. Modify your block to contain the code shown in Listing 8.
Listing 8. The script block, modified to accommodate the RemoteObject instead of HTTPService
		import mx.collections.ArrayCollection;
		import mx.automation.codec.ArrayPropertyCodec;
		import com.flexandair.ContactVO;
		import mx.controls.Alert;
		import mx.utils.ArrayUtil;
		[Bindable] public var dp:ArrayCollection;
			public function handleContacts(event:ResultEvent):void {
				dp = new ArrayCollection(ArrayUtil.toArray(event.result));
				myDG.dataProvider = dp;
			public function handleFault(event:FaultEvent):void {, event.fault.faultCode);
			public function saveContact():void {
				var newContact:ContactVO = new ContactVO(); = nameInput.text; = emailInput.text; = phoneInput.text;
			public function handleSave(event:ResultEvent):void {
				nameInput.text = '';
				emailInput.text = '';
				phoneInput.text = '';
The script block begins with several import statements, which are necessary for the application to run. Below the import statements is a variable declaration, dp. This variable is defined as an ArrayCollection, and it will hold the contact objects you receive from Zend_Amf.
As you can see, below the import statements and variable declaration, all the methods referred to in the RemoteObject are created. First, the handleContacts() method accepts the array of contacts that Zend_Amf returns. The array is converted to the ArrayCollection you defined earlier, dp, and that in turn is set as the data provider for the DataGrid. Next, there is the handleFault() function, which simply displays an alert box containing relevant information whenever a fault is encountered. The third function, saveContact(), assembles a new ContactVO object. The properties of the object are populated with values from the form. The object is then sent to the Zend_Amf server, where it is inserted into the database.
The last function, handleSave(), refreshes the data grid by calling getContacts from the RemoteObject again. The form is then cleared so that another contact can be entered. Again, the file is terminated with a closing </mx:Application> tag.
Before you can run the application, however, you must create the ContactVO class in ActionScript. To do so, right-click the src folder beneath the XMLandPHP project in Flex Builder, and then choose New > Folder. In the dialog box that appears, locate the text box near the bottom, and type com/flexandair/, as shown in Figure 7.



Figure 7. Creating a new folder in Flex Builder
Click Finish, and the new folder structure appears beneath the src folder in the left pane of Flex Builder. Right-click the flexandair folder, and then choose New > ActionScript Class. In the dialog box that appears, specify ContactVO as the name, and leave the other options set to their defaults. Click Finish. The new ActionScript class should appear in the right pane of the window. Delete the text and paste the code shown in Listing 9 in its place.
Listing 9. The ContactVO object defined in ActionScript package com.flexandair
	public class ContactVO
		public var id:int;
		public var name:String;
		public var email:String;
		public var phone:String;
		public function ContactVO()

As you can see, this ActionScript file largely mirrors its PHP counterpart, Contact.php. The notable exception is the bindable element [RemoteClass(alias="ContactVO")]. These lines let Zend_Amf know that the alias for this class is ContactVO, thereby enabling the ActionScript-to-PHP class mapping. Save the project and run it. Your browser opens and displays something like Figure 8.



Figure 8. The Zend_Amf client running
When a new contact is added, the data grid is refreshed to reflect the change. The form is then cleared.
Note If you receive an error, it could be a result of the Flash Player security sandbox. To circumvent this error, copy the crossdomain.xml file from the attached archive to the web root directory of your web server. Again, DO NOT use this file in a production environment, as it allows remote access from any host.
Now that you've got Zend_Amf up and running, you can expand your services to include virtually any PHP method. What's more, you can now access any of the powerful extensions in the Zend Framework for use in your Flex applications. To find out more about the Zend Framework, check out the Zend Framework home page. For more information on using Flex with PHP, visit Adobe's Flex and PHP Developer Center.
About the author: Richard Bates is a Web application developer and consultant in Athens, GA. For the last 8 years, Richard has worked in this capacity in a wide spectrum of industries, with clients ranging from telecom and health care to leisure and real estate. He currently works as a Flex/AIR and PHP developer with XIG Networks, focusing on e-commerce and interactive promotional applications. He has a blog, at