#749: Middleware should work as a 'stack' or allow custom orderings
-------------------------------------+--------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Core framework
Version: | Resolution:
Keywords: | Stage: Design decision
needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
-------------------------------------+--------------------------------------
Comment (by lukeplant):
Another idea: allow middleware to add additional arbitrary information to
the response objects so that they can see whether they have already
modified the response (and require implementations to use this facility
where necessary). This data would have to survive serialisation, and we
would need to think about how it would work for response objects that are
not subclasses of 'HttpResponse'.
--
Ticket URL: <http://code.djangoproject.com/ticket/749#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---