Re: New editors' copy of the Web Services Architecture Glossary available

Hi, I have a question about this part of the definition,
<snip>"Note: a gateway may or
may not be a SOAP node; however a gateway is never a SOAP intermediary,
since gateways terminate messages and SOAP intermediaries relay them
instead. Being a gateway is typically a permanent role, whilst being a
SOAP intermediary is message specific."</snip>



Why can't gateway act as a SOAP intermediary?  Doesn't that just mean that
that particular gateway
implementation chose not to modify the message it terminated when it sent
it out? Is a gateway
REQUIRED to modify the message? Why? Is a gateway NOT allowed to treat
protocols/messages
specifically?

This doesn't match up well to my laymans understanding...

Whats the difference between 'terminate and send the same messsage' and
'relay'?

Heather Kreger
Web Services Lead Architect
STSM, SWG Emerging Technology
kreger@us.ibm.com
919-543-3211 (t/l 441)  cell:919-496-9572


Mark Baker <distobj@acm.org>@w3.org on 10/28/2002 12:04:34 PM

Sent by:    www-ws-arch-request@w3.org


To:    www-ws-arch@w3.org
cc:
Subject:    Re: New editors' copy of the Web Services Architecture Glossary
       available




Hi Hugo,

I see that the definition of "gateway" that we came up with didn't make
it into this version.  Perhaps you could incorporate it in at a
convenient time.

Here's what I believe is the latest, incorporating input from
Jean-Jacques and DaveH [1][2][3];

"Gateway: a node that terminates a message on an inbound interface with
the intent of presenting it through an outbound interface as a new
message. Unlike a proxy, a gateway receives messages as if it were the
final receiver for the message. Due to possible mismatches between the
inbound and outbound interfaces, a message may be modified and may have
some or all of its meaning lost during the conversion process. For
example, an HTTP PUT has no equivalent in SMTP.  Note: a gateway may or
may not be a SOAP node; however a gateway is never a SOAP intermediary,
since gateways terminate messages and SOAP intermediaries relay them
instead. Being a gateway is typically a permanent role, whilst being a
SOAP intermediary is message specific."

The tricky bit would be deciding which section to put it in.  It isn't
SOAP-specific, so Section 7 seems the wrong place, but it would be nice
to fit it with other protocol-related definitions.  Perhaps you could
rename Section 7 to "Protocol Definitions", and perhaps 7.1 to
"Core Protocol Concepts" or something like that ...?  I don't really
care, just pointing out the issue.

 [1] http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0180
 [2] http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0181
 [3] http://lists.w3.org/Archives/Public/www-ws-arch/2002Oct/0194

MB

On Thu, Oct 24, 2002 at 07:32:34PM +0200, Hugo Haas wrote:
>
> Hi all.
>
> A new version of the glossary is available for comments at:
>
>
http://dev.w3.org/cvsweb/~checkout~/2002/ws/arch/glossary/wsa-glossary.html?rev=1.12&content-type=text/html

>
> The terms have been organized, the suggestions from the mailing list
> have been incorporated, etc. A detailed list of changes can be found
> at [1].
>
> The document contains a section for choreography terms containing
> proposals from the discussion that occurred those past few days.
>
> Needless to say that the whole document is very much work in progress.
>
> Please note the intro section which describes the process that the
> Working Group agreed to regarding terminology.
>
> Regards,
>
> Hugo
>
>   1. http://dev.w3.org/cvsweb/2002/ws/arch/glossary/wsa-glossary.xml
> --
> Hugo Haas - W3C
> mailto:hugo@w3.org - http://www.w3.org/People/Hugo/

--
Mark Baker, CTO, Idokorro Mobile.  Ottawa, Ontario, CANADA.
http://www.markbaker.ca             http://www.idokorro.com

Received on Monday, 28 October 2002 12:37:08 UTC