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

Joerg Schad updated MESOS-3256:
-------------------------------
    Description: 
Currently the http requests in libprocess/http.hpp are named post(), put(), and 
get(). This naming scheme did not for the addition of delete with Mesos-3152 as 
delete is a C++ keyword and hence that call was named deleteRequest.

We should come up with a consistent naming scheme which is easily 
understandable.

One potential solution would be to have only one request method accepting a 
`Request` object. See 
https://issues.apache.org/jira/browse/MESOS-3763?focusedCommentId=14969636&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14969636.

  was:
Currently the http requests in libprocess/http.hpp are named post(), put(), and 
get(). This naming scheme did not for the addition of delete with Mesos-3152 as 
delete is a C++ keyword and hence that call was named deleteRequest.

We should come up with a consistent naming scheme which is easily 
understandable.


> Consistent naming of http request methods.
> ------------------------------------------
>
>                 Key: MESOS-3256
>                 URL: https://issues.apache.org/jira/browse/MESOS-3256
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Joerg Schad
>
> Currently the http requests in libprocess/http.hpp are named post(), put(), 
> and get(). This naming scheme did not for the addition of delete with 
> Mesos-3152 as delete is a C++ keyword and hence that call was named 
> deleteRequest.
> We should come up with a consistent naming scheme which is easily 
> understandable.
> One potential solution would be to have only one request method accepting a 
> `Request` object. See 
> https://issues.apache.org/jira/browse/MESOS-3763?focusedCommentId=14969636&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14969636.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to