api - REST - Shouldn't PUT = Create and POST = Update -


shouldn't put used create , post used update since put idempotent.

that way multiple puts same order place 1 order?

the fundemental difference put known resource, , therefor used updating, as stated here in rfc2616.

the fundamental difference between post , put requests reflected in different meaning of request-uri. uri in post request identifies resource handle enclosed entity. resource might data-accepting process, gateway other protocol, or separate entity accepts annotations. in contrast, uri in put request identifies entity enclosed request -- user agent knows uri intended , server must not attempt apply request other resource. if server desires request applied different uri

i see coming based on names however.

i @ post should uri handle content of request (in cases params form values) , creating new resource, , put uri subject of request (/users/1234), resource exists.

i believe nomenclature goes long ways, consider web. 1 might want post message message board, , put additional content message @ later date.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -