> > If the objective is to seperate the two systems why is having the URL > system know about Models more acceptable than having the Model system > know about URLs? This is most certainly a bike shed IMO. > The objective is not to completely separate the two. URLs are roughly the "Controller" in the MVC world, and need to know about both the models and the views. It is the "glue" that binds the two together. URLs already do know about models and that will remain.
It is having models know about what URLs that is a circular dependency that is both unneeded and problematic. Models should stand alone and be usable by any number of applications within the same project. Having the models be responsible for knowing how they are being presented does not allow for unanticipated uses of those models. I'll leave it at that for now if you still think it is merely the repainting of the bike shed. Pat McNerthney ClearPoint Metrics, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
