W3C home > Mailing lists > Public > xml-dist-app@w3.org > April 2011

Re: SOAP and Cacheability

From: Noah Mendelsohn <nrm@arcanedomain.com>
Date: Tue, 19 Apr 2011 09:13:10 -0400
Message-ID: <4DAD8A66.9010008@arcanedomain.com>
To: Unmesh Joshi <unmeshjoshi@gmail.com>
CC: xml-dist-app@w3.org
The SOAP 1.2 specifications added features to allow use of 
application/soap+xml as a media type with HTTP GET as well as POST; 
unfortunately, those features were as far as I know not supported by the 
major implementations, and so are not in practice available to users. Had 
GET been supported, then HTTP caching should have worked in the normal 
manner, and indeed that would be one reason for supporting and using the 


On 4/15/2011 12:25 AM, Unmesh Joshi wrote:
> Hi,
> One of the key features of HTTP which help it scale at internet level
> is ability to cache responses.
> There is decent amount of caching facilities built into standard and
> well understood by web infrastructure.
> Because SOAP uses HTTP as one of the transport protocols, it can not
> get benefit of any of these caching mechanisms.
> If cacheability is to be provided, it needs to be built by application.
> Was there any plan to build caching facilities at SOAP protocol level
> which could be understood by SOAP processing agents?
> Thanks,
> Unmesh
Received on Tuesday, 19 April 2011 13:13:36 UTC

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