Hi. Got a question for you about an idea on making urlconfs more sophisticated and dynamic.
First some background: We are (re) developing a rather complex collection of sites. We have a live Zope system currently, with a lot of extensions to it's code, it works but it reached it's architectural limits. We like Django architecture. The problem we face now is it's kind of static url to view matching system. Current site is dynamically edited, up to folders and domains. Our content is rather large and the site is quite busy. We can't afford restart the application for new url paths as this will be a burden on our deployment procedure (development environments, qa environments, production environments.) Also we in principle we wouldn't like a single generic view for every path and then do all our own way like many do. And anyway currenttly it doesn't deal with multiple hosts/domains. The idea: We've been thinking on extending/changing the conf.url code and the resolver code to support some method call to resolve a full url (not just the path, but the host and domain too.) This could be achieved using an "urlpatterns object" (instead of a list as currently returned by pattern()). It might end up needing to move the regex matching at the urlconf level. So the RegexURLResolver.resolve() code should move the iteration to the "urlpatterns object" itself. This could open the door for dynamically configured urls including host, dynamically loads of views. It's a crude idea, and definetly not something final. But would love to listen what Django experts would think about it. Thanks! Alejo --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
