Re: Updated SOAP HTTP GET binding document


I assume that this was your response to my question about how which
bindings should be used;

"There are a variety of other HTTP methods and common method prefixes
that could be mapped. For example, a setStockPrice SOAP Method could be
mapped to the HTTP PUT method."

Rather than "could" (which I interpret as "MAY"), I'd like to see a
"SHOULD" in there.  Otherwise you'll have people sending getFoo()
methods over PUT, setFoo() methods over POST, etc..

I believe that saying this is *very* important; IMO, more important
than doing a GET binding.



On Mon, May 06, 2002 at 07:33:50PM -0700, David Orchard wrote:
> I decided to get rid of the dates considering that this is really an
> "editors" draft and I didn't want lots of versions floating around.
> Numerous updates based upon discussions at the TAG F2F, and comments from
> Larry Masinter and Mark Baker.
> Cheers,
> dave

Mark Baker, Chief Science Officer, Planetfred, Inc.
Ottawa, Ontario, CANADA.

Received on Monday, 6 May 2002 22:51:25 UTC