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

[Stanley Stanev]

I agree that General != ambiguous and all was fine until you described the example of yours IMHO, if you change GetStockQuote from real-time to delayed then you can make some of your consumers angry and a new version or even new operation could be a good idea Do not forget that every service has SLA as well. If your response time was 3secs with the old real-time GetStockQuote and now the response time is 15secs then things may not look that good to your consumers anymore. thanks, Stanley Stanev MomentumSI Mark Baker wrote: Stanley, On 10/3/06, Stanley Stanev <[EMAIL PROTECTED]com> wrote: > Very general interfaces could be a problem the same as very open contracts in life are :) General != ambiguous. General means that f() can undergo significant change without needing to change the interface. Consider if f() were a stock quote retrieval function. Had the interface to that function been GetRealtimeStockQuote, then a change to f() to, say, return delayed stock quotes would require a new interface for obvious reasons. On the other hand, if the interface were just GetStockQuote, then that change in f() would *not* require a new interface. Mark. __._,_.___ 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 __,_._,___