I have a large legacy application which passes around the request to nearly every method.
Reading this source is no fun. In about 95% of all cases "request" is not used, but "request.user" is needed for permission checking. Example: there is a drop down box with the list of possible actions the user can perform now. The list of actions is filtered according to the logged in request.user. I want to get rid of the ugly passing around "request" from method to method. I have some ideas in mind, but won't post them today. I am afraid that if I would, the discussion would be only pro/contra my solution. But I guess there is a third way :-) -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/fc2c1d65-fa3d-461b-9846-3802cf153e15%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.