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

RE: WSA constraints

From: Anne Thomas Manes <anne@manes.net>
Date: Mon, 23 Sep 2002 17:11:45 -0400
To: "Mark Baker" <distobj@acm.org>
Cc: <www-ws-arch@w3.org>, <mark.baker@sympatico.ca>
Message-ID: <ECEDLFLFGIEENIPIEJJPMEHKCHAA.anne@manes.net>

It depends on what you classify as a SOAP intermediary. From my reading of
the SOAP 1.2 spec, every SOAP Header processor is an intermediary, even
though the all the processors run within the context of the final
destination SOAP server. But the SOAP server isn't the recipient. The SOAP
service is the recipient. I think lots of people are using SOAP header
processors today.

> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Mark Baker
> Sent: Monday, September 23, 2002 12:04 PM
> To: Anne Thomas Manes
> Cc: www-ws-arch@w3.org; mark.baker@sympatico.ca
> Subject: Re: WSA constraints
>
> Anne, thanks for the technical feedback!
>
   <snip>

> I did think about this for a while, and could have gone either way, but
> SOAP's processing model is explicitly layered, so that convinced me that
> it was a reasonable constraint.  I could be convinced otherwise,
> however, since few (if any) Web services use SOAP intermediaries.
>
Received on Monday, 23 September 2002 17:11:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:06 GMT