- From: Paul Downey via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 10 Jun 2005 23:16:40 +0000
- To: public-ws-desc-eds@w3.org
Update of /sources/public/2002/ws/desc/wsdl20 In directory hutz:/tmp/cvs-serv32138/2002/ws/desc/wsdl20 Modified Files: wsdl20-primer.xml Log Message: added section on evolving a service Index: wsdl20-primer.xml =================================================================== RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v retrieving revision 1.89 retrieving revision 1.90 diff -C2 -d -r1.89 -r1.90 *** wsdl20-primer.xml 22 May 2005 14:10:13 -0000 1.89 --- wsdl20-primer.xml 10 Jun 2005 23:16:37 -0000 1.90 *************** *** 1405,1408 **** --- 1405,1427 ---- particular benefits where an agent may quickly tell if a service has changed by simply comparing the namespace value.</p></div3> + <div3 id='ad-versioing-migration'><head>Evolving a Service</head> + <p> + Compatible changes are far more easily managed than incompatible ones: + </p> + <ulist> + <item> + <p> + With a compatible change the service need only support the latest version of a service. A client may continue to use a service adjusting to new version of the interface description at a time of its choosing. + </p> + </item> + <item> + <p> + With an incompatible change, the client receives a new version of the interface description and is expected to adjust to the new interface before old interface is terminated. Either the service will need to continue to support both versions of the interface during the hand over period, or the service and the clients are co-ordinated to change at the same time. An alternative is for the + client to continue until it encounters an error, at which point it uses the new version of the interface. + </p> + </item> + </ulist> + + </div3> <div3 id="adv-versioning-combined">
Received on Friday, 10 June 2005 23:16:46 UTC