Mark,
Well, I didn't mention WS-Everything and didn't want to get into a
sterile debate over the merits of various technical approaches.
I was just trying to challenge your statement that coordination costs
for the GET operation in REST are effectively zero.
What you now seem to be saying is that the coordination costs for GET
are the same ("identical") as for a custom-designed interface with WS-
Everything.
This sounds more plausible and I tend to agree with you.
-Mike.
--- In [email protected], "Mark Baker"
<[EMAIL PROTECTED]> wrote:
>
> On 11/27/06, Mike Glendinning <[EMAIL PROTECTED]> wrote:
> > --- In [email protected], "Mark
Baker"
> > <distobj@> wrote:
> > >
> > > There are many advantages depending upon what angle you're
looking at
> > > it from - caching, security, reliability, etc.. In general
though, I
> > > think the big one is that any HTTP client anywhere can turn
that URI
> > > into data using GET. If POST were used, then clients would
also have
> > > to know *what* to POST, removing that benefit. Coordination
costs are
> > > less (effectively zero) using GET.
> > >
> > > Mark.
> > >
> >
> > But how do I know what to do with the data that is returned by
GET?
>
> How would you know what to do with the data returned from a Web
> service endpoint that you invoked getStockQuote() on? Same answer.
> The *only* difference between the two situations is that you're
using
> a more general operation when you use GET. Everything else is
> *identical*.
>
> Mark.
>
