Re: Issue 169: Propose http method in the operation interface to simplify http binding.

On Mon, Jul 12, 2004 at 02:01:35PM -0700, David Orchard wrote:
> We could come up with our own "CRUD" definitions and then say that C=POST, R=GET, U=PUT, D=DELETE when bound to HTTP.

Any constrained interface you come up with will either be less general
than the REST interface (by definition), or equivalent to it.  CRUD is
less general.  For example, that mapping above fails to expose POST
functionality which permits for things like data processing, annotation,
insertion, etc..

> I don't know what "GET on" means because I don't have a binding.

You don't need a binding, you can look up its meaning in the HTTP
specification.  It means, retrieve a representation of the resource
identified by that URI.

>  It could mean "get the mail for".

Well, technically, it only means what I said above.  But it could
certainly be *used* to return the mail for  Good call.

>  I also don't know whether that's safe or not.  

Why not?  GET can be assumed safe by a Web client.


Received on Monday, 12 July 2004 21:27:39 UTC