--- Gregg Wonderly <[EMAIL PROTECTED]> wrote:
> I think that interface based access is a key feature > of a well designed SOA. > There must be an interface (like or implementation) > description which properly > and completely identifies the type of data going in > and out of a service operation. It should be possible for a client of that service to detect an > incompatibility and it should be possible for a > service to assert an incompatable change if needed. > > These things make it much more likely that > incompatibilities do not create imaginary (service responds okay to invalid request) or incorrect operations service misinterprets data and acts inappropriately) in your SOA. > > Gregg Wonderly > With COM, interfaces never change if published, new functionalities are exposed through new interfaces to the COM object. So it won't break current clients who won't use newly added interfaces while new clients may use the new interfaces. So nothing breaks. THis mechanism could be implemented in Services that have multiple interfaces. Jerry __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/service-orientated-architecture/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
