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

Re: Gateways

From: Mark Baker <distobj@acm.org>
Date: Fri, 11 Oct 2002 15:50:05 -0400
To: Jean-Jacques Moreau <moreau@crf.canon.fr>
Cc: www-ws-arch@w3.org
Message-ID: <20021011155005.O8458@www.markbaker.ca>


On Fri, Oct 11, 2002 at 09:22:24AM +0200, Jean-Jacques Moreau wrote:
> I've just re-read your definition, and I think I'm starting to 
> understand your point-of-view. I'm seeing things slightly 
> differently (but I don't claim a lot of expertise in HTTP gateways).
> With that proviso, how would you best describe Host II in figure 
> 2.2 [1] ? Could this be an HTTP gateway?

I don't believe so.  I'd say that the diagram accurately refers to it as
an HTTP proxy.

I'm pretty sure that a HTTP gateway cannot be a SOAP intermediary,
because SOAP and HTTP are at the same layer in the protocol stack, and
therefore share an addressing model (when bound).

> > I think we need to pick one definition and run with it.  What I proposed
> > isn't perfect, but I think it's good enough to go with for now.
> I think yours doesn't carry as clearly the notion that a gateway 
> terminates a message. The following sentence was certainly 
> enlightening to me: "Unlike a proxy, a[n HTTP] gateway receives 
> requests as if it were the origin server for the requested resource".

Ok.  Do you want to propose an edit that would make that clearer?

> > (P.S. while I'm talking to you, ws-desc issue #65 isn't mine 8-)
> You're quite correct; yet another effect of the cut-and-paste 
> syndrome. Corrected (thanks to Google).


Mark Baker, CTO, Idokorro Mobile.  Ottawa, Ontario, CANADA.
http://www.markbaker.ca             http://www.idokorro.com
Received on Friday, 11 October 2002 15:48:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:05:41 UTC