- From: Champion, Mike <Mike.Champion@SoftwareAG-USA.com>
- Date: Mon, 1 Jul 2002 12:07:19 -0400
- To: www-ws-arch@w3.org
> -----Original Message----- > From: Champion, Mike [mailto:Mike.Champion@softwareag-usa.com] > Sent: Monday, July 01, 2002 11:57 AM > To: www-ws-arch@w3.org > Subject: RE: SOAP and the Web (was RE: Late binding) > > > but seriously, what is the RESTically correct aproach to the > transaction/reliability/security/etc. problem? Multiple > PUT/GETs to establish a shared context within which to interpret > messages and transaction/transmission state? That is, mightn't some future standardization of SOAP headers be GET or PUT as resource representations of the state of the complex transaction in a RESTful MEP, even though they would be simply POSTed in a more RPC-like MEP? I'm looking for a web services architecture that shares as much as possible, even if there continues to be considerable disagreement on the most effective MEPs.
Received on Monday, 1 July 2002 12:07:40 UTC