Mailing-List: contact ambari-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ambari-dev@incubator.apache.org
Date: Fri, 26 Oct 2012 22:45:12 +0000 (UTC)
From: "Hitesh Shah (JIRA)" <jira@apache.org>
To: ambari-dev@incubator.apache.org
Message-ID: <737006234.33884.1351291512613.JavaMail.jiratomcat@arcas>
In-Reply-To: <1139434149.33116.1351279152565.JavaMail.jiratomcat@arcas>
Subject: [jira] [Updated] (AMBARI-930) Map update to PUT and create to POST
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AMBARI-930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hitesh Shah updated AMBARI-930:
-------------------------------

    Assignee: John Speidel
    
> Map update to PUT and create to POST
> ------------------------------------
>
>                 Key: AMBARI-930
>                 URL: https://issues.apache.org/jira/browse/AMBARI-930
>             Project: Ambari
>          Issue Type: 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