[
https://issues.apache.org/jira/browse/AMBARI-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hitesh Shah updated AMBARI-930:
-------------------------------
Issue Type: Sub-task (was: Task)
Parent: AMBARI-666
> Map update to PUT and create to POST
> ------------------------------------
>
> Key: AMBARI-930
> URL: https://issues.apache.org/jira/browse/AMBARI-930
> Project: Ambari
> Issue Type: Sub-task
> Reporter: John Speidel
> Assignee: John Speidel
> Attachments: AMBARI-930.patch
>
>
> Changed the mapping for update and create.
> Although the previous approach was corrrect technically I feel that it is
> better to be simple for our case. The decision to use PUT or POST comes down
> to idempotency of the operation since the HTTP 1.1 spec states that PUT is
> always idempotent and POST has no such guarantees. This ties into caching and
> performance but at the load that would be expected for an Ambari server, this
> isn't really an issue. So I have now used a 1-1 mapping between crud
> operations and http verb. This will be easier for the api developer to
> determine which verb to use.
> So to be explicit:
> Create = POST
> Update = PUT
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
