Open Stack

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150808/0ae1ed59/attachment.pgp>