Forest Bond wrote: > But your model code shouldn't have HTTP-related bits buried in it. That's a > layering violation. That code should raise a more generic exception that your > view code converts to an HTTP response.
Yes, this is may be more correct way. But having one exception without a conversion chain is just simpler. I'm fine with calling it AccessDenied instead of Http403 :-). Though thinking of this now I'm not that sure that it should be in Django by default, it smells more like a custom solution... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
