Comments on: N:1 Web Service Applications – Getting from V1 to V2 http://www.goland.org/webservicesn1versioning/ Technology, Politics, Food, Finance, etc. Mon, 23 Jan 2012 17:37:17 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Yaron http://www.goland.org/webservicesn1versioning/comment-page-1/#comment-827 Yaron Wed, 28 Jul 2004 09:47:40 +0000 #comment-827 <br/>Please, feel free to reference it. <br/><br/>TDD - I think TDD is interesting but I suspect it won't prove enough for backwards compatibility. The issue I point out in the article is that the test matrix for backwards compatibility is enormous. So in a sense I'm assuming that the developers are doing something like TDD but the number of tests needed to capture all the edge case behaviors of the clients as they interact with the service for V1 are just too many to be useful enumerated. In most cases, where dropping V1 clients isn't an option, just leaving the V1 code alone is probably the most productive option.<br/><br/>Facade? Proxy? Intermediary? - I used the term intermediary because it has a nice web service sound. It really was a rather arbitrary choice. Please, feel free to reference it.

TDD – I think TDD is interesting but I suspect it won't prove enough for backwards compatibility. The issue I point out in the article is that the test matrix for backwards compatibility is enormous. So in a sense I'm assuming that the developers are doing something like TDD but the number of tests needed to capture all the edge case behaviors of the clients as they interact with the service for V1 are just too many to be useful enumerated. In most cases, where dropping V1 clients isn't an option, just leaving the V1 code alone is probably the most productive option.

Facade? Proxy? Intermediary? – I used the term intermediary because it has a nice web service sound. It really was a rather arbitrary choice.

]]> By: Paul Downey http://www.goland.org/webservicesn1versioning/comment-page-1/#comment-828 Paul Downey Wed, 28 Jul 2004 07:04:52 +0000 #comment-828 <br/><br/>Yaron, that's an interesting walk through. i'd like to reference this in a paper i'm writing on practical versioning if that's OK.<br/><br/>Test Driven Development is the answer to removing the fear of rewriting - i guess you may have already seen Tim Bray's TDD sermon: <br/>http://www.tbray.org/ongoing/When/200x/2004/06/13/TDD2004<br/><br/>i wonder if the term 'facade' or 'proxy' is better than 'intermediary' here since you're describing an agent invisible to the sender.<br/><br/>as you point out, branching is the killer, and there is no silver bullet here.. Yaron, that's an interesting walk through. i'd like to reference this in a paper i'm writing on practical versioning if that's OK.

Test Driven Development is the answer to removing the fear of rewriting – i guess you may have already seen Tim Bray's TDD sermon:
http://www.tbray.org/ongoing/When/200x/2004/06/13/TDD2004

i wonder if the term 'facade' or 'proxy' is better than 'intermediary' here since you're describing an agent invisible to the sender.

as you point out, branching is the killer, and there is no silver bullet here..

]]>