On Wed, Nov 24, 2010 at 12:31 PM, Paul McLanahan <[email protected]> wrote: > I created ticket #14770 (http://code.djangoproject.com/ticket/14770) > because I ran into a situation this week where I only had access to > the request, but needed to set a cookie. As the ticket says, I did > solve this problem with a middleware, but I couldn't think of a reason > not to include this ability in core.
Ugh, I'm -1 on this. It confuses requests and responses, and abstracts away a *very* important aspect of how HTTP actually works. Doing this is semantically unclean and binds together two parts of the request/response cycle that are separate by design. I don't at all like the idea of obscuring the truth about how HTTP actually works. There's a tiny chance I might be able to be convinced to change my mind, but you'll have to back up and explain exactly what it is you're trying to do that's impossible without this hack. Jacob -- You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en.
