-
Notifications
You must be signed in to change notification settings - Fork 32
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
Comments
Looking forward to your PR @codingjoe ! 😜 |
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.. |
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
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.
The text was updated successfully, but these errors were encountered: