Thinking through Adrian's post and mine above, it appears to be a trade off between coupling in the framework and increased responsibility for user views code. Personally I would opt for the former, because IMHO the idea of a framework is to reduce responsibility of user code and promoting same sets of design patterns for common problems (rather than each similar program having different adhoc ways to deal with the same problems I.e rather than having different ways people would implement a catch all view, have views send the same signal if the given arguments were not interpretable.) first before anything else, otherwise what else can a framework provide?.
-- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
