On Mon, Apr 14, 2008 at 2:00 PM, James Bennett <[EMAIL PROTECTED]> wrote:
> > On Sun, Apr 13, 2008 at 6:05 AM, Amit Upadhyay <[EMAIL PROTECTED]> wrote: > > I was wondering about the reason that middleware classes were used > instead > > of decorators to implement middleware functionality. > > There are two cases, each with drawbacks: > > 1. Whatever system is available to provide additional processing is by > default applied only to a single specific view (e.g., a decorator). > The drawback is that you will inevitably want an easy way to say > "apply this everywhere" instead of manually applying the decorator to > every view. ... SNIP ... You got me wrong. I am talking about pre-applying the "middleware-decorators" to all views found thru urls.py processing. -- Amit Upadhyay Vakow! www.vakow.com +91-9820-295-512 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
