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

[Radovan Janecek]

Hey Mark,

what are you talking about? It's likely that, at some point, a service evolves in such a way that requires interface change. It's not a failure, it's life. Otherwise, RSS evolution is a failure or HTML evolution is a failure - just to name few ;-)

I would be interested in whether your 'maximum amount' means 'all' or 'a lot'? Btw, didn't you announce some time ago you are switching only to Atom? Didn't your blog's interface change then?

Cheers,
Radovan

On 9/29/06, Mark Baker <[EMAIL PROTECTED]> wrote:

On 9/28/06, Michael Poulin <[EMAIL PROTECTED]> wrote:
>
> Mark wrote: " Never."
> May I ask: why?

Because I always endeavour to maximize loose coupling by separating
the concerns of implementation from the concerns of interface. If
f(x) changes such that the interface needs to change/be-versioned,
then I have failed. Hence, I use very general interfaces that can
withstand the maximum amount of implementation variation.

Mark.

--
Radovan Janecek
http://radovanjanecek.net/blog __._,_.___

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

__,_._,___