W3C home > Mailing lists > Public > www-ws-desc@w3.org > November 2003

RE: What WSDL defines - the diagram!

From: <paul.downey@bt.com>
Date: Tue, 4 Nov 2003 18:50:43 -0000
Message-ID: <2B7789AAED12954AAD214AEAC13ACCEF0FFF1D30@i2km02-ukbr.domain1.systemhost.net>
To: <distobj@acm.org>
Cc: <www-ws-desc@w3.org>
ah, but the pipe is the transport. 
try:  ls | zcat | sort
 
Paul

	-----Original Message----- 
	From: Mark Baker [mailto:distobj@acm.org] 
	Sent: Tue 04/11/2003 17:32 
	To: Downey,PS,Paul,XSJ67A C 
	Cc: www-ws-desc@w3.org 
	Subject: Re: What WSDL defines - the diagram!
	
	

	On Tue, Nov 04, 2003 at 04:31:00PM -0000, paul.downey@bt.com wrote:
	> i thought the 'protocol' was described by the binding  and MEP being used
	> - but i guess that would mean we could start to debate what 'protocol' actually means :-)
	
	Yep, that's a toughie.  I'm not going there. 8-)
	
	> there does come a point when you're so losely coupled, you're not actually coupled at all..
	
	Sort like "ls" and "sort"; no coupling at all, except that both are
	developed to an abstraction with a single uniform semantic which permits
	state to be transferred from one to the other, ala "ls | sort".  That's
	exactly the kind of loose coupling that I want Web services/SOA to have.
	But it's not what we've got.  It *requires* a constrained interface,
	because that is how the common abstraction is reified.  In Unix, that
	abstraction is the "pipe".  In Linda, it's the "space".  In the Web it's
	the "resource".  In email, it's the "mailbox".  SOA needs one of those.
	
	Mark.
	--
	Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca

	

Received on Tuesday, 4 November 2003 13:50:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:27 GMT