Re: [service-orientated-architecture] if f(x) changes, do you version the service?

[Chuck D'Antonio]

I'd be partial to versioning the service in this instance if the difference in the result is semantically distinct.  By returning a result that has changed semantics, you're changing the contract of the service. Anytime the contract changes I'd suggest that that represents a new version of the service.   For an example, let's start with f(x) returning the square root of x.  If f(4) was returning 1.78 and you fixed it to return 2, then I'd say that's not a new version.  If you changed your algorithm so that f(4) returned the cube root of 4, and that was the correct purpose of the function with the business changes that drove it, then I'd say it's a new version.  You've changed the expectations inherent in the contract so you should use version the service to make that clear. Chuck Chuck D' Antonio Software Consulting Professional Mobile: (617) 388-1120 Email: [EMAIL PROTECTED] IM: dantonioJr (AIM)  http://www.linkedin.com/in/dantonio     On Sep 27, 2006, at 9:33 AM, jeffrschneider wrote: If the logic in a service is changed and f(x) begins producing a new result, do you version the service? (Note: in this scenario, the interface didn't change just the internal logic.) Thanks, Jeff __._,_.___ SPONSORED LINKS Computer software program Computer software spy Computer job Database software Discount computer software Your email settings: Individual Email|Traditional Change settings via the Web (Yahoo! ID required) Change settings via email: Switch delivery to Daily Digest | Switch to Fully Featured Visit Your Group | Yahoo! Groups Terms of Use | Unsubscribe __,_._,___