Using the following code, a blob storage container can be created on development storage.

Using the following code, a blob storage container can be removed from development storage.

Using the following code, a blob can be uploaded to a blob storage container on development storage. Note that the container has already been created before.

Using the following code, a blob can be copied from inside the storage account. The advantage of using this method is that the copy operation occurs in the Azure cloud and does not involve downloading the blob. Note that the container has already been created before.

Using the following code, a blob can be downloaded from a blob storage container on development storage. Note that the container has already been created before and a blob has been uploaded.

By default, blob storage containers on Windows Azure are protected from public viewing. If any user on the Internet should have access to a blob container, its ACL can be set to public. Note that this applies to a complete container and not to a single blob!

Using the following code, blob storage container ACL can be set on development storage. Note that the container has already been created before.

http://phpstorage.blob.core.windows.net/phpazuretestshared1?st=2009-08-17T09%3A06%3A17Z&se=2009-08-17T09%3A56%3A17Z&sr=c&sp=w&sig=hscQ7Su1nqd91OfMTwTkxabhJSaspx%2BD%2Fz8UqZAgn9s%3D
        

When you are the owner of a Windows Azure Bob Storage account, you can create and distribute a shared access key for any type of resource in your account. To do this, the generateSharedAccessUrl() method of the Zend_Service_WindowsAzure_Storage_Blob storage client can be used.

The following example code will generate a Shared Access Signature for write access in a container named "container1", within a timeframe of 3000 seconds.

The following example code will generate a Shared Access Signature for read access in a blob named test.txt in a container named "container1" within a time frame of 3000 seconds.

When you receive a Shared Access Signature from someone else, you can use the Windows Azure SDK for PHP to work with the addressed resource. For example, the following signature can be retrieved from the owner of a storage account:

http://phpstorage.blob.core.windows.net/phpazuretestshared1?st=2009-08-17T09%3A06%3A17Z&se=2009-08-17T09%3A56%3A17Z&sr=c&sp=w&sig=hscQ7Su1nqd91OfMTwTkxabhJSaspx%2BD%2Fz8UqZAgn9s%3D
            

The above signature gives write access to the "phpazuretestshared1" "container" of the phpstorage account. Since the shared key for the account is not known, the Shared Access Signature can be used to work with the authorized resource.

Note that there was no explicit permission to write to a specific blob. Instead, the Windows Azure SDK for PHP determined that a permission was required to either write to that specific blob, or to write to its container. Since only a signature was available for the latter, the Windows Azure SDK for PHP chose those credentials to perform the request on Windows Azure blob storage.

Using the following code, a table can be created on Windows Azure production table storage.

Using the following code, a list of all tables in Windows Azure production table storage can be queried.

To enforce a schema on the client side using the Zend_Service_WindowsAzure_Storage_Table class, you can create a class which inherits Zend_Service_WindowsAzure_Storage_TableEntity. This class provides some basic functionality for the Zend_Service_WindowsAzure_Storage_Table class to work with a client-side schema.

Base properties provided by Zend_Service_WindowsAzure_Storage_TableEntity are:

• PartitionKey (exposed through getPartitionKey() and setPartitionKey())

• RowKey (exposed through getRowKey() and setRowKey())

• Timestamp (exposed through getTimestamp() and setTimestamp())

• Etag value (exposed through getEtag() and setEtag())

Here's a sample class inheriting Zend_Service_WindowsAzure_Storage_TableEntity:

The Zend_Service_WindowsAzure_Storage_Table class will map any class inherited from Zend_Service_WindowsAzure_Storage_TableEntity to Windows Azure table storage entities with the correct data type and property name. All there is to storing a property in Windows Azure is adding a docblock comment to a public property or public getter/setter, in the following format:

Let's see how to define a propety "Age" as an integer on Windows Azure table storage:

Note that a property does not necessarily have to be named the same on Windows Azure table storage. The Windows Azure table storage property name can be defined as well as the type.

The following data types are supported:

• Edm.Binary - An array of bytes up to 64 KB in size.

• Edm.Boolean - A boolean value.

• Edm.DateTime - A 64-bit value expressed as Coordinated Universal Time (UTC). The supported DateTime range begins from 12:00 midnight, January 1, 1601 A.D. (C.E.), Coordinated Universal Time (UTC). The range ends at December 31st, 9999.

• Edm.Double - A 64-bit floating point value.

• Edm.Guid - A 128-bit globally unique identifier.

• Edm.Int32 - A 32-bit integer.

• Edm.Int64 - A 64-bit integer.

• Edm.String - A UTF-16-encoded value. String values may be up to 64 KB in size.

To use the Zend_Service_WindowsAzure_Storage_Table class without defining a schema, you can make use of the Zend_Service_WindowsAzure_Storage_DynamicTableEntity class. This class inherits Zend_Service_WindowsAzure_Storage_TableEntity like an enforced schema class does, but contains additional logic to make it dynamic and not bound to a schema.

Base properties provided by Zend_Service_WindowsAzure_Storage_DynamicTableEntity are:

• PartitionKey (exposed through getPartitionKey() and setPartitionKey())

• RowKey (exposed through getRowKey() and setRowKey())

• Timestamp (exposed through getTimestamp() and setTimestamp())

• Etag value (exposed through getEtag() and setEtag())

Other properties can be added on the fly. Their Windows Azure table storage type will be determined on-the-fly:

Optionally, a property type can be enforced:

The Zend_Service_WindowsAzure_Storage_Table class automatically works with Zend_Service_WindowsAzure_Storage_TableEntity if no specific class is passed into Table Storage methods.

Queries in Zend_Service_WindowsAzure_Storage_Table table storage can be performed in two ways:

• By manually creating a filter condition (involving learning a new query language)

• By using the fluent interface provided by the Zend_Service_WindowsAzure_Storage_Table

Using the following code, a table can be queried using a filter condition. Note that the table and entities have already been created before.

Using the following code, a table can be queried using a fluent interface. Note that the table and entities have already been created before.

This topic demonstrates how to use the table entity group transaction features provided by Windows Azure table storage. Windows Azure table storage supports batch transactions on entities that are in the same table and belong to the same partition group. A transaction can include at most 100 entities.

The following example uses a batch operation (transaction) to insert a set of entities into the "testtable" table. Note that the table has already been created before.

Using the following code, a queue can be created on development storage.

Using the following code, a queue can be removed from development storage.

Using the following code, a message can be added to a queue on development storage. Note that the queue has already been created before.

Using the following code, a message can be read from a queue on development storage. Note that the queue and message have already been created before.

The messages that are read using getMessages() will be invisible in the queue for 30 seconds, after which the messages will re-appear in the queue. To mark a message as processed and remove it from the queue, use the deleteMessage() method.

Using the following code, a queue can be checked for new messages. Note that the queue and message have already been created before.

Note that messages that are read using peekMessages() will not become invisible in the queue, nor can they be marked as processed using the deleteMessage() method. To do this, use getMessages() instead.