SOAP intermediaries must be explicitly targetted by the message
(using the 'actor' attribute). In this respect, they are completely
unlike the OPES model.
Of course, other kinds of intermediaries (HTTP, etc.; they may even
be interposed with the SOAP intermediary) may make other decisions
about messages and what to do to them.
On Tue, Jul 10, 2001 at 09:57:50AM -0500, Brian E Carpenter wrote:
> Web Services intermediaries will certainly exist and use SOAP; whether
> they are exactly like the current OPES model is still unclear. Indeed
> the security/integrity problems have to be solved, and this is more
> fundamental than debating the ICAP hammer and the SOAP screwdriver.
>
> Brian
>
> Keith Moore wrote:
> >
> > > Several of us have long believed that with an OPES framework, multiple
> > > existing remote procedure call protocols including iCAP and SOAP can
> > > be added to an authenticated and authorized intermediate proxy model.
> >
> > so by adding components that can alter data in transit, you're going
> > to increase the level of integrity? right.
> >
> > Keith
>
--
Mark Nottingham, Research Scientist
Akamai Technologies (San Mateo, CA USA)
