Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Django Middleware to WSGI Middleware #9

Closed
Miserlou opened this issue Feb 16, 2016 · 4 comments
Closed

Move Django Middleware to WSGI Middleware #9

Miserlou opened this issue Feb 16, 2016 · 4 comments

Comments

@Miserlou
Copy link
Owner

It was pointed out during the Q & A that the Django Middleware could be replaced with a WSGI Middleware that would live in Zappa core. This has a number of obvious benefits, such as more shared code, less client-specific code, and less client-specific integration.

@codingjoe
Copy link
Contributor

👍 eventually this will also allow you to hook any WSGI application on lambda

@Miserlou
Copy link
Owner Author

Looking forward to your PR @codingjoe ! 😜

@Doerge
Copy link
Contributor

Doerge commented Feb 20, 2016

I have written an initial WSGI middleware for flask-zappa.

It's not quite there yet, but I'm still working on it. If anyone want to give it a spin with Django it can be found here..

@Miserlou
Copy link
Owner Author

Excellent work! Werkezeug was a good choice, and I'm happy to see the middleware moving upstream.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants