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

Re: SOAP and the Web architecture

From: Paul Prescod <paulp@ActiveState.com>
Date: Mon, 27 Aug 2001 20:28:47 -0700
Message-ID: <3B8B0FEF.E746AADF@ActiveState.com>
To: xml-dist-app@w3.org
Hugo Haas wrote:
> GET and POST, for HTML forms, address different problems.


> The same way it makes sense to use POST sometimes instead of GET (and
> vice versa) for HTML forms, I think that the use of SOAP over HTTP
> POST sometimes makes sense, and sometimes does not.


> I will note that, depending on the kind of request which is done, it
> might not be achievable with GET even though it's idempotent, e.g. if
> the data structures are very complex.

Arguable. What spec. restricts the complexity of data sent through GET?
I agree that there are various social expectations that URIs be simple
and short and also that there may be some software that is poorly set up
to handle long complex ones. But I'm not sure how much of this problem
is really real and how much is merely expectation. Maybe if SOAP pushed
the limits a little we could find out what HTTP software is really
broken and fix it.

Anyhow, I would be satisfied if SOAP allows me to access simple web
services with simple parameters in a simple way (i.e. through a URI) and
if I need to deal with complex data I'll move on to more complex
solutions. Most idempotent web services will have short, simple
parameters just as most idempotent web sites do.
Take a recipe. Leave a recipe.  
Python Cookbook!  http://www.ActiveState.com/pythoncookbook
Received on Monday, 27 August 2001 23:29:23 UTC

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