Updates the visibility time-out of a message and/or the message contents. Retrieves a message from the front of the queue, without changing the message visibility.ĭeletes a specified message from the queue. Retrieves a message from the queue and makes it invisible to other consumers. You may also specify -1 for this parameter to indicate that the message should remain in the queue until dequeued and deleted. Sets stored access policies for the queue that can be used with shared access signatures.Īdds a message to the queue and optionally sets a visibility time-out for the message. This is new with api-version : For the Queue service, the Put Message API now allows a time-to-live value in the messagettl parameter of over seven days. Returns details on any stored access policies specified on the queue. Returns queue properties, including user-defined metadata. This operation is available only on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account. Retrieves statistics related to replication for Queue Storage. Queries the Cross-Origin Resource Sharing (CORS) rules for Queue Storage before sending the request. The REST API for Queue Storage includes these operations: Operation You can then store a reference to the data as a message in a queue. If you need to store messages larger than 64 KB, you can store message data as a blob or in a table. 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. For earlier versions, the maximum size of a message is 8 KB. Each message can be up to 64 KB in size for version or later. Azure Queue Storage stores messages that can be read by any client that has access to the storage account.Ī queue can contain an unlimited number of messages.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |