I'm no expert in this area, but perhaps we could use a thread-local middleware to keep request handy?
Sort of like this wiki solution [1] but put the whole request into _thread_locals. Would there be any performance downside in doing that? Is it safe to do that? This would solve the reverse URL construction issue of this discussion thread, along with request.urlconf not being able to be used in permalinks [2] and the url template tag [3] It should be mandatory Middleware, not optional (I've written something related to that in my latest patch in #987 [4] - by the way, Malcolm, have you checked that patch out yet?). [1] http://code.djangoproject.com/wiki/CookBookThreadlocalsAndUser [2] http://code.djangoproject.com/ticket/3530 [3] http://code.djangoproject.com/ticket/5034 [4] http://code.djangoproject.com/ticket/987 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
