Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Jai Haridas — Mon, 21 Nov 2011 23:53:14 GMT

@Vikram,

MessageUpdateFields enum is declared as flags. To update both content and visibility, have you tried setting it to:

MessageUpdateFields.Content | MessageUpdateFields.Visibility

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Vikram — Mon, 21 Nov 2011 18:10:02 GMT

I just downloaded the Nov 2011 release 1.6 Azure SDK and tried to use the UpdateMesasge method to update the content of a queue message. If i set the 'MessageUpdateFields' to 'MessageUpdateFields.Content' then it raises the exception 'Calls to UpdateMessage must include the Visibility flag' and if I set it to 'MessageUpdateFields.Visibility' it just dones not update the message contents.

Any idea what is going on?

Thanks.

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Jai Haridas — Sun, 13 Nov 2011 18:35:03 GMT

@Adar, thank you for the feedback. We will look at providing this functionality in the storage client library, to abstract that away.

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Adar Wesley — Sun, 13 Nov 2011 16:44:21 GMT

Hi,

Why isn't there a way to block on the GetMessage method until a message is available?

A blocking version of GetMessage with an optional timeout parameter would be very nice.

---

Adar Wesley

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

ChrisL — Thu, 22 Sep 2011 02:02:03 GMT

@Ravi - My initial thoughts exactly when reading this blog

@Jai - Thanks for the link. Although the hyperlink is TL;DR, the conclusion looks promising and I'll review it more when I need queueing. I hope MSFT Eugne from PnP is using that code, seems like something of his quality.

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Jai Haridas — Tue, 20 Sep 2011 09:20:39 GMT

@Ravi, Thanks for the feature request. We have noted it down in the list of feature requests to consider in the future. You can also look at using client side abstractions that makes this simpler (windowsazurecat.com/.../implementing-storage-abstraction-layer-to-support-very-large-messages-in-windows-azure-queues)

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Ravi — Mon, 19 Sep 2011 16:23:12 GMT

If the best practise to store large messages (>64kb) is a combination of storing the key in the queue and the message in the BLOB, cant you make this as your internal implementation and drop the message size limitation for a message in the queue?

re: Windows Azure Queues: Improved Leases, Progress Tracking, and Scheduling of Future Work

Vin — Sat, 17 Sep 2011 17:02:03 GMT

I have been conducting a lot of Azure workshops, and just wanted to say a big thanks for these improvements !!. Customers will be very happy in my next boot camp . Kudos to the Storage team !