Indeed, it's clean and goes well with Django design principles.. However if I need to track just a few updates a day on a single model or admin form, the extra thousands or millions of calls generated by middleware(on every single request), it is really hard to chew.. at least one needs to be aware of this penalty. Otherwise really good point again! For a broader use I'd go for your solution, my usecase is a bit different tough.
Cheers Andy! On Jan 4, 4:04 am, Andy McKay <a...@clearwind.ca> wrote: > On Mon, Jan 2, 2012 at 12:25 PM, Waldek Herka > <waldek.he...@googlemail.com>wrote: > > > c) local threading way posted by you is not as straight > > forward as it looks - I'd say it's very similar in complexity to > > mine.. you still need to explicitly call 'activate' somewhere(view > > method) > > Middleware can do that just fine. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
