[
https://issues.apache.org/jira/browse/MESOS-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-3920:
-------------------------------
Description:
Right now, the "reserve" and "unreserve" endpoints work as follows:
1. slaveID and resources are sent as two separate key-value pairs in the body
of the request, which is URL-encoded ({{application/x-www-form-urlencoded}}
media type).
2. resources is itself a JSON document.
This is a bit weird: it would more idiomatic to send a single JSON document
(using content-type {{application/json}}) with the required information. [
Updated: the initial bug description claimed that slaveID and resources were
sent as query parameters, but that is incorrect. ]
Obviously, there are some backward compatibility concerns if we want to change
this.
was:
Right now, the "reserve" and "unreserve" endpoints work as follows:
1. slaveID and resources are sent as two separate key-value pairs in the body
of the request, which is URL-encoded ({{application/x-www-form-urlencoded}}
media type).
2. resources is itself a JSON document.
This is a bit weird: it would more idiomatic to send a single JSON document
(using content-type {{application/json}}) with the required information.
Obviously, there are some backward compatibility concerns if we want to change
this.
> Considering changing /reserve, /unreserve endpoint syntax
> ---------------------------------------------------------
>
> Key: MESOS-3920
> URL: https://issues.apache.org/jira/browse/MESOS-3920
> Project: Mesos
> Issue Type: Bug
> Reporter: Neil Conway
> Priority: Minor
> Labels: http, mesosphere, reservations
>
> Right now, the "reserve" and "unreserve" endpoints work as follows:
> 1. slaveID and resources are sent as two separate key-value pairs in the body
> of the request, which is URL-encoded ({{application/x-www-form-urlencoded}}
> media type).
> 2. resources is itself a JSON document.
> This is a bit weird: it would more idiomatic to send a single JSON document
> (using content-type {{application/json}}) with the required information. [
> Updated: the initial bug description claimed that slaveID and resources were
> sent as query parameters, but that is incorrect. ]
> Obviously, there are some backward compatibility concerns if we want to
> change this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
