Webservice versioning
"A new version of a Web service contract that continues to support consumer programs
designed to work with the old version is considered backwards-compatible. From a design
perspective, this means that the new contract has not changed in such a way that it can
impact existing consumer programs that are already using the contract.
A simple example of a backwards-compatible change is the addition of a new operation
to an existing WSDL definition ..."
http://www.infoq.com/resource/articles/Web-Service-Contracts/en/resources/ERL_WSContractVersioning_013613517X_20-22.pdf
designed to work with the old version is considered backwards-compatible. From a design
perspective, this means that the new contract has not changed in such a way that it can
impact existing consumer programs that are already using the contract.
A simple example of a backwards-compatible change is the addition of a new operation
to an existing WSDL definition ..."
http://www.infoq.com/resource/articles/Web-Service-Contracts/en/resources/ERL_WSContractVersioning_013613517X_20-22.pdf
Comments