Re: Issue 5; GET vs GetLastTradePrice

>
> > If I dereference a "service name" and get a body of
> > description on how to access that service, isn't
> > that body still describing, at the end of the day, some
> > syntax and some semantics?
>
> Sure.  SOAP and WSDL aren't solving the world's problems, they are
basically
> just removing some of the mechanical impediments to describing and
invoking
> object interfaces across platforms, languages, vendors, etc. Just as the
> hypertext Web generally works because there is an intelligent human
reading
> the rendered HTML, SOAP and WSDL work because there are intelligent humans
> doing the mapping from the syntax level they describe to the semantics of
> the underlying code.
>

Right.  I was trying to tease out some specifics of how this "middle ground"
approach yields a net reduction in development effort.  It's not about
solving
the world's problems, understood.  For this particular claim, I'm trying to
understand how there would be any net reduction in work.  Maybe I've skewed
things by introducing the term "net"?  My other comment that you didn't
understand was saying the same thing: integration effort comes from
interface
complexity, which AFAIK is a factor addressed by REST but not by
WSDL/SOAP, whose focus and tool support kick in somewhere later in
the design process?

Walden

Received on Thursday, 2 January 2003 13:17:44 UTC