Hi all,
In the original post
https://groups.google.com/d/topic/django-developers/eJFuiWdobbY/discussionI
presented a problem with the current Django middleware archticture and
how it can lead to "*leaks*" in the handling of responses and exceptions. I
also proposed an alternative architecture
Hi all,
I'd like to get some discussion going on the subject of Django's middleware
architecture.
The current way middleware works provides a way for a developer to specify
code executed at certain stages of the arrival of the request and the
departure of the response from the system. This is
On 15/11/13 18:42, Erik van Zijst wrote:
> How do people feel about this approach and should it be merged into
> Django? If not, then I can turn it into a library instead. Maybe at our
> size we're not in Django's sweet spot anymore. However, in their current
> version the recommended hashers are
