Re: [WhenToUseGet-7] Re: TAG document: SOAP HTTP GET binding avai lable

I personally feel that both of these proposals are inadequate in
important ways; Content-Location because it requires an unsafe method
invocation in order to discover the URI, and construct-a-URI because
it breaks opacity and is not at all a general solution.

Would it really be so hard to just say "don't do RPC"?  Most of the Web
services proponents I've talked to are trying to distance themselves
from RPC.  I wouldn't expect that there'd be as much push back on it
now, as there would have been when the XMLP WG was chartered.  We could
even show examples of how to use SOAP & HTTP GET together, such as the
one I put together last year; http://www.markbaker.ca/2001/07/SoapUses/

I think that it's at least worth considering as a solution.

MB
-- 
Mark Baker, CTO, Idokorro Mobile (formerly Planetfred)
Ottawa, Ontario, CANADA.               distobj@acm.org
http://www.markbaker.ca        http://www.idokorro.com

Received on Tuesday, 21 May 2002 08:04:27 UTC