W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2001

RE: SOAP actor model

From: Williams, Stuart <skw@hplb.hpl.hp.com>
Date: Thu, 22 Mar 2001 14:03:32 -0000
Message-ID: <5E13A1874524D411A876006008CD059F192320@0-mail-1.hpl.hp.com>
To: "'frystyk@microsoft.com'" <frystyk@microsoft.com>, "Williams, Stuart" <skw@hplb.hpl.hp.com>, "'Mark Nottingham'" <mnot@akamai.com>
Cc: "'Mark Jones'" <jones@research.att.com>, xml-dist-app@w3.org
Hi Henrik,

> -----Original Message-----
> From: Henrik Frystyk Nielsen [mailto:frystyk@microsoft.com]
> Sent: 21 March 2001 16:35
> To: 'Williams, Stuart'; 'Mark Nottingham'
> Cc: 'Mark Jones'; xml-dist-app@w3.org
> Subject: RE: SOAP actor model
> >I'd be interested to know of there has been any deployment of 
> >SOAP based solutions that involve SOAP intermediaries and 
> >routing of SOAP messages through intermediaries. I think it 
> >would be instructive for many of us if someone were able to 
> >describe the practical deloyment of such a configuration and 
> >how message routing issues were addressed in a particular case.
> The interesting thing about this point is that *if* this is the case
> then they are able to use the current SOAP composability model which I

Where is the best articulation of this model? I have not been able to find
it articulated in the SOAP 1.1 specification.

> would take as a sign that at least it is possible to do it without
> support in the core protocol.
> There are several ways in which I can imagine this being done 
> btw and if
> it is possible to layer then I strongly suggest that it should be. 
> Henrik 


Received on Thursday, 22 March 2001 09:03:58 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:12 UTC