-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ivan Fedorov wrote:
>>URL_RESOLVER = "django.core.urlresolvers.RegexURLResolver" > > +1 > >>You could do very nice things with this approach, like using a database >>to resolve the url, or even change the other settings depending on the >>hostname you resolve... > > > I'm already have database-driven URL Resolver. It's built over standard > Django resolver, so anybody can use it with unmodified Django. > > Does anybody interesting in it?.. Maybe something for contrib ? I'm working on a patch for the URL_RESOLVER. This patch will include a the default behaviour as django.core.urlresolvers.URLResolver and a simple HostURLResolver, that allows matching for hostnames, too. URLResolver is just a small wrapper, because i changed the paramters for the resolver to be def __init__(self, request, urlconf_name): Maybe even remove the urlconf_name and look it up in the resolver class rather then the http base class. What do you think ? The HostURLResolver is so small, that i think it doesn't make sense to put it into contrib. kindly regards Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: GnuPT 2.7.2 Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDwWMhy/mkIQp7AD0RAh5zAJ42iWYOgzQ5vMjfLk3lLx3a99lIWACgj6M9 06QNiFOQh5SOUH9+OoIH10g= =ZgV3 -----END PGP SIGNATURE-----
