On Fri, 17 Jun 2016, Sylvain Bauza wrote:
In the review, you explain why you don't trust Routes and I respect that.
That said, are those issues logged as real problems for our API consumers,
which are mostly client libraries that we own and other projects we know,
like Horizon ?
The implication of your question here is that it is okay to do HTTP
incorrectly if people don't report problems with that lack of
correctness?
If that is a problem for those, is there something we could improve, instead
of just getting rid of it ?
When I found the initial problem with Routes, it was because I was
doing some intial nova testing (with gabbi-tempest[1]) and
discovered it wasn't returning a 405 when it should. I made a bug
https://bugs.launchpad.net/nova/+bug/1567970
and tried to fix it but Routes fought me. If someone else can figure
it out more power to them.
In any case selector's behavior in this case is just better. Better
is better, right?
--
Chris Dent (╯°□°)╯︵┻━┻ http://anticdent.org/
freenode: cdent tw: @anticdent__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
