> I hate to say it, but Routes and most of the other schemes presented > _do_ feel over-engineered. The current URL patterns system is fast > and clean.
I actually agree 100%. And my earlier post indeed smacks of overengineering. And in my current smallish project I don't intend to do any of that kind of encapsulation. With that said, I do think that the issue has legs if you were to pull in 3 or 4 or 5 projects from different sources to create some kind of new all-encompassing proejct. E.g., Admin, ShoppingCart, Inventory, and PayPayIntegration. (Assuming those to be 3rd party apps). It certainly doesn't need to be solved for me to use Django, though. See? As I promised, I've overthought this whole thing. I _must_ learn to think more agile. :-( --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
