On Feb 25, 2006, at 8:15 PM, Ron Schmelzer wrote: > So, can you ever truly be "decoupled"?
IMHO, true decoupling is reached when the only semantics the consumer needs to know to use a given service are those that it takes to understand the task in general (regardless of which service). IOW, in order to order a pizza you need to understand the basics of ordering and what it is that you want to order (pizza). This knowledge, a uniform API and the ability of the service to show the path through the application at runtime should be sufficient to substitute the service by any other. Ah - you also need a way for the service to tell the client that it's expectation (order pizza) cannot be met (should that be the case). Jan ________________________________________________________________________ _______________ Jan Algermissen, Consultant & Programmer http://jalgermissen.com Tugboat Consulting, 'Applying Web technology to enterprise IT' http://www.tugboat.de Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> 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/
