Microsoft Makes API Changes to Azure Storage Service

Microsoft has released a number of API changes within its Azure Storage Service. The REST APIs for the service offer programmatic access to blob, queue, table, and file service in both Azure and development environments. Any app that can send and receive HTTP/HTTPS requests and responses can access Storage Services and the new API features.

A new API, the Incremental Copy Blob API, was introduced. The new API enables efficient copying and backup of page blob snapshots. The blob service provides storage for certain entities (e.g. binary files, text files, etc.). A container is a set of blobs and every blob must belong to a container.

Put Message API returns now include information regarding recently added messages. An example of the newly added information is the PopReceipt element which allows a developer to call an updated message or deleted message regarding messages in the queue. Other elements within the Put Message API response body include InsertionTime, ExpirationTime, and TimeNextVisible.

The Files API now accepts a parameter that limits listings to a specific prefix. The four resources include storage account, shares, directories, and files. The Files service is accessible via the SMB protocol and REST APIs.

The timeout query parameter is now accepted and enforced by all Table Storage APIs. The Table service allows users to offer structured storage in the form of tables. Prior to this release, the timeout query parameter was not accepted within the Table services.

In addition to API-level changes, Microsoft added a number of feature and capacity changes for the service in general. Block sizes increased to 100 MB, which enables block blobs up to 4.77 TB. Additionally  the .NET Client Library was updated for all new added features. To keep up to date with all changes, follow the Azure Storage Service site

Be sure to read the next Storage article: Dropbox API v1 Officially Retired

 

Comments (0)