RE: Protocol independence

If I send "hello" with HTTP PUT, I am requesting that the string
be stored at the URI.

If I send "hello" with HTTP POST, I am requesting that the processor
identified by the URI to which I'm POSTing, process that string.

Those HTTP messages have *exactly* the same body, yet they mean
*very* different things.

QED.

Acknowledging I'm right on this doesn't necessarily mean you have
to abandon Web services, of course (as much as I'd recommend doing
so 8-).  I think it would be quite reasonable for the arch doc to
just say something like this as a result;

"Though envelopes sent over application protocols differ in meaning
depending upon which application protocol and method is used, the WSA
prescribes that application protocols shall be treated as if they were
transport protocols.  This has the following advantages and
disadvantages; [...]"

Sound good?

MB

Received on Tuesday, 8 April 2003 11:02:44 UTC