Thanks everyone for your feedback. I think we have a consensus that this
sort of change would be best left to v2 of the API. We can start planning
v2 of the API at the Paris summit, and target some kind of “community
preview” of it to be released as part of Kilo.
On 8/29/14, 11:02 AM, Everett
On Aug 28, 2014, at 3:08 AM, Flavio Percoco fla...@redhat.com wrote:
Unfortunately, as Nataliia mentioned, we can't just get rid of it in
v1.1 because that implies a major change in the API, which would require
a major release. What we can do, though, is start working on a spec for
the V2 of
On 08/27/2014 06:33 PM, Nataliia Uvarova wrote:
I doesn't support the idea of removing this endpoint, although it
requires some efforts to maintain.
First of all, because of the confusion among users, that it could bring.
The href to message is returned in many cases, and was seen as
Crew, as we continue implementing v1.1 in anticipation for a “public preview”
at the summit, I’ve started to wonder again about removing the ability to GET a
message by ID from the API. Previously, I was concerned that it may be too
disruptive a change and should wait for 2.0. But consider
I doesn't support the idea of removing this endpoint, although it
requires some efforts to maintain.
First of all, because of the confusion among users, that it could bring.
The href to message is returned in many cases, and was seen as canonical
way to deal with it. (As far as I understand,
