On Fri, Aug 07 2015, Michael Krotscheck wrote: > Here's the thing. If the middleware is _optional_ like keystone auth, then > including it via paste.ini makes way more sense. In fact, keystone auth has > gone to great lengths to have no dependencies for that very same reason. > If, instead, the middleware is a feature that should ship with the service > - like CORS, or a simple caching layer - then it should be baked into your > application initialization directly.
Except that AFAIU you cannot use keystonemiddleware neither without hardcoding its usage pattern (even if it's optional) in your code in the same way you're talking about with CORS. Which is then terrible. -- Julien Danjou # Free Software hacker # http://julien.danjou.info
signature.asc
Description: PGP signature
__________________________________________________________________________ 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
