On Dec 28, 2004, at 3:18 PM, Josh Sled wrote:
> It's hard to say generally, but I think you're seeing two different
> things:
>
> * an inherent similarity in the two methods, including a bit of a
> semantic overlap with respect to PUT's specification of ability to
> create things.
>
> * the fact that there's two different levels of REST:
> GET+POST-does-everything-else vs. GET/PUT/POST/DELETE. Not
> differentiating the two can lead to confusion about which "POST"
> is being used/described. [1]
...
> [1]:
> http://asynchronous.org/blog/archives/2004/08/25/levels_of_rest.html

Josh, while that may be your theory (and you are welcome to it), the
notion that there are two levels of REST is completely false. There
are different extents to which a REST-based application will use HTTP
methods, but that doesn't mean the architectural style has two different
sets of constraints. The application is either obeying the REST
constraints or it is not, and POST in particular has the meaning
"process this" regardless of how REST-compliant it may be because
REST does not define the meaning of POST (HTTP does).

....Roy