On 11/27/06, Mike Glendinning <[EMAIL PROTECTED]> wrote:
> 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.

That's not what I'm saying, Mike.  By "identical" I was referring to
other issues you have to deal with, such as processing the data.  But
simplifying coordination is most definitely a big part of what
generalization gives you.

As I say, the knowledge required to use POST is *more* because it has,
in effect, an extra "parameter" that the caller has to know about, and
know the value of; the HTTP body.  The GET has no such parameter in
order to be used; you just need a URI (which you also need for POST).

It all comes down to reusing existing agreements; the more you are
able to reuse, the easier things are to coordinate with those who also
follow those agreements.  GET already means "get me data", while POST
does not.

Mark.

Reply via email to