[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Categories of Web Service messages: data-oriented v s acti

• To: Mike Champion <mc@x...>
• Subject: Re: Categories of Web Service messages: data-oriented v s action-oriented
• From: Francis Norton <francis@r...>
• Date: Tue, 05 Feb 2002 11:46:42 +0000
• Cc: xml-dev@l...
• References: <YWQO3X2X94TRQN636395GBPD0A6EB2.3c5f2f06@MChamp>
• Reply-to: francis@r...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2

Hi Mike,

Mike Champion wrote:
 >
 > Message exchange patterns are closely related to the issue of
 > "coupling, and  this is brought out in the rant against the RPC
 > paradigm that someone recently  posted a link to 
http://www.omnifarious.org/~hopper/technical/corbabad.html
 >
I know nothing about CORBA, but I agree with you that the higher success 
of protocols over APIs is a coupling issue, and in fact I'd go further 
and say it's nothing to do with sync/async. For me, the simple problem 
is that an API gives closer coupling between content and transport, 
whereas a protocol give looser coupling. Message structures change 
independently from transport details, so why link them? That's why I 
push document-oriented messaging for business web services.

Francis.

• References:
  • RE: Categories of Web Service messages: data-oriented v saction-oriented
    • From: Mike Champion <mc@x...>

• Prev by Date: Re: Getting rid of entities (was: misprocessing namespaces)
• Next by Date: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Previous by thread: Re: Categories of Web Service messages: data-oriented v saction-oriented
• Next by thread: RE: Categories of Web Service messages: data-oriented v s action-oriented
• Index(es):
  • Date
  • Thread