Windows Azure Services Management versioning

1.Windows Azure ' s Service Management Versioning

Operations provided by the Service Management APIs may have multiple versions. You must specify the version of a operation that's want to use by setting the X-ms-version request header. Requests without an x-ms-version header would be rejected and return a (+) bad Request response. If your service calls an older version of a operation, can choose to continue calling the older version, or modify Yo ur code to call a newer version. Any differences in functionality between versions is outlined in the documentation for the API call.

Note:

Windows Azure is a public platform, so in order to meet different versions of the application to provide different versions of the API, then how to tell the HTTP request to invoke which version of the API? The X-ms-version parameter that sets the request header. Whether you are an older version or a new version, you can call the appropriate API based on the parameters you set, as long as you set the X-ms-version parameter of the request header.

The x-ms-version request header value must is specified in the format yyyy-mm-dd.

For example:

Request headers:x-ms-version:2011-02-25

Summarize:

The cloud platform is a public service platform, so it is necessary to keep the various versions of the API to meet the application call needs of all enterprises and individuals, and to better meet the application's upgrade and extension, as long as the x-ms-version parameter is assigned in the request header in order to know the version of the API.

This article is from the "Love Coffee" blog, please be sure to keep this source http://4837471.blog.51cto.com/4827471/1575222

Windows Azure Services Management versioning