If you have any question left, please drop a note with the discussion link of this page.
Web Services migration strategy
From Wiki.zanox.com
A new Web Services migration strategy will take effect at the end of May, 2010. This strategy consists of the following:
- Each API release will be shut off one year following the release of a subsequent version. In effect, this means that with every new release, developers have one year to migrate to the new version. This is a liberalizing of the previous strategy, where a version was cut off one year after its release, and a slight revision from previous communication. At the end of May, 2010, the 2009-02-01 Version will be shut off, because the subsequent Version 2009-05-01 was in May 2009.
- The API default URLs will always point to the latest API versions. Since the release of Version 2009-02-01 in February 2009, http://api.zanox.com/xml/__SOME_RESOURCE__ has pointed to http://api.zanox.com/xml/2009-02-01/__SOME_RESOURCE__, even following subsequent releases. At the end of May, 2010, http://api.zanox.com/xml/__SOME_RESOURCE__ will point to http://api.zanox.com/xml/2009-07-01/__SOME_RESOURCE__ and http://api.zanox.com/xml/2009-02-01/__SOME_RESOURCE__ will no longer be available.
What does this mean for Web Services developers?
The 2009-07-01 Version was a significant milestone: we introduced zanox Connect and with it the ability to submit an application to the Application Store. This affected the signature of every API call.
Changes in subsequent versions should be more incremental:
- If you make calls directly to a Web Services API using the default URL, you should not need to change your code when new versions are introduced.
- If you make calls using a client library, we strongly recommend you upgrade your library every time a new version is released, but you will likely not be required to change the calls your application code makes to the library.