W3C home > Mailing lists > Public > www-ws-arch@w3.org > March 2002

RE: Summary: D-G0017

From: Cutler, Roger (RogerCutler) <RogerCutler@chevrontexaco.com>
Date: Wed, 27 Mar 2002 12:00:36 -0800
Message-ID: <3B286631A9CFD1118D0700805F6F9F5A09D09CFC@hou281-msx1.chevron.com>
To: "'Joseph Hui'" <jhui@digisle.net>
cc: www-ws-arch@w3.org
OK by me, but I have to admit that I don't understand the distinction that
you are making.
I have found the following definitions (extracting only the relevant parts),
for the two words:

Protocol - A standard procedure for regulating data transmission between
Mechanism - An instrument or a process, physical or mental, by which
something is done or comes into being.

What is limiting about having a standard "process by which reliable
messaging is done"?  Or is it just that "protocol" is more specifically a
comp sci word?  I must admit to having a personal preference for using, when
possible, simple words in their common meaning rather than technical terms,
but I certainly would not insist on it.  Does "mechanism" have a
specifically comp sci meaning of which I am unaware?  
My background is physics, which has a strong tradition of using simple words
when possible, so bear with me ...
-----Original Message-----
From: Joseph Hui [mailto:jhui@digisle.net] 
Sent: Wednesday, March 27, 2002 1:35 PM
To: Cutler, Roger (RogerCutler)
Cc: www-ws-arch@w3.org
Subject: RE: Summary: D-G0017

Hi Roger,
> DAG0017
> Measurements:
> Is there a standard mechanism for implementing reliable messaging?
I believe the word "mechanism" should be replaced with "protocol."
It's a bad thing to standardize mechanisms.  It stymies creativity.
(Standardizing protocols and formats is a good thing, OTOH.)
Joe Hui
Exodus, a Cable & Wireless service
 -----Original Message-----
From: Cutler, Roger (RogerCutler) [mailto:RogerCutler@chevrontexaco.com]
Sent: Wednesday, March 27, 2002 10:57 AM
To: www-ws-arch@w3.org
Subject: Summary: D-G0017


The reference architecture should provide guidance for the development the
web services infrastructure needed for implementing common business

Is there a standard mechanism for implementing reliable messaging? 
Transaction processing?  
Routing and intermediaries? 
Is there a standard way to uniquely identify and order messages involved
with a web service? 
Received on Wednesday, 27 March 2002 15:02:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:40:55 UTC