On Fri, 17 Apr 2015, Julien Danjou wrote:
After using Pecan for a while, I'm leaning toward explicit routing too. This Falcon API looks right too. Honestly Pecan is messy. Most of the time, when coding, you have no clue which one of the method is going to be picked in which controller class.
Yes, and there's no straightforward way (that I can find) to dump the available routes (which is handy for testing, debugging, documenting, etc). While Falcon's style is a clear step in the right direction I think it would be even better with a slight extension (which may already exist, if it doesn't it would be easy to make): Load the route mappings from a file so you (as a human) can have a single index into code. A few years ago I was completely in love with selector[1] because all it did was delegate an incoming WSGI request to one of several WSGI callables based on request method and parameterized paths. [1] https://github.com/lukearno/selector/ -- Chris Dent tw:@anticdent freenode:cdent https://tank.peermore.com/tanks/cdent __________________________________________________________________________ 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
