RE: Intermediaries - various cases

>The pub/sub node is an intermediary, because it both sends and receives
>messages.  But it's also the final-destination/service-provider.

But SOAP 1.2, section 1.4.3, says: "An ultimate SOAP receiver cannot also be
a SOAP intermediary for the same SOAP message".

Ugo

-----Original Message-----
From: Mark Baker [mailto:distobj@acm.org]
Sent: Thursday, September 26, 2002 8:15 PM
To: Ugo Corda
Cc: 'www-ws-arch@w3.org'
Subject: Re: Intermediaries - various cases


I'll give my 2c on this.  Good questions, BTW.

On Thu, Sep 26, 2002 at 02:37:41PM -0700, Ugo Corda wrote:
>  Or is the publish-and-subscribe
> node the Service Provider, which engages in separate interactions with the
> subscriber nodes?

Yes, that one.

The pub/sub node is an intermediary, because it both sends and receives
messages.  But it's also the final-destination/service-provider.

There are different kinds of intermediaries; some will be final
destinations (gateways), and others will be routed-to (forward proxies
ala WS-Routing) or routed-from (reverse proxies, ala WS-Referral).

> Or is there no single answer to these questions, and it
> all depends on the logical view that I want to apply to the scenario?

There's definitely more than one way to design and/or execute a route of
nodes to achieve some goal.  But in each case, I believe all the roles
should be apparent.

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com