Caution: The documentation you are viewing is
for an older version of Zend Framework.
You can find the documentation of the current version at docs.zendframework.com
Zend_Service_WindowsAzure_Storage_Queue - Zend_Service
The Queue service stores messages that may be read by any client who has access to the storage account.
A queue can contain an unlimited number of messages, each of which can be up to 8 KB in size. Messages are generally added to the end of the queue and retrieved from the front of the queue, although first in/first out (FIFO) behavior is not guaranteed. If you need to store messages larger than 8 KB, you can store message data as a queue or in a table and then store a reference to the data as a message in a queue.
Queue Storage is offered by Windows Azure as a REST API which is wrapped by the Zend_Service_WindowsAzure_Storage_Queue class in order to provide a native PHP interface to the storage account.
This topic lists some examples of using the Zend_Service_WindowsAzure_Storage_Queue class. Other features are available in the download package, as well as a detailed API documentation of those features.
Using the following code, a queue can be created on development storage.
Example #1 Creating a queue
Using the following code, a queue can be removed from development storage.
Example #2 Deleting a queue
Using the following code, a message can be added to a queue on development storage. Note that the queue has already been created before.
Example #3 Adding a message to a queue
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.
Example #4 Reading a message from a queue
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.
Example #5 Marking a message as processed
Using the following code, a queue can be checked for new messages. Note that the queue and message have already been created before.
Example #6 Check if there are messages in a queue
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.