I would prefer the root view solution.
Url reversing is more complex than the current setup allows. For example predefined values in the routing setup are allowed, the reverse url tag should be able to access these (think about setting https=1, then https url would be generated (-1:http url, 0: depending on current url => no full url needed)). But I'm sure other people can think of other peculiarities. This is why I prefer the root_view solution, as it would allow for a more plugged approach. As it stand now, the url-reversing is too much tied to django, while it is relatively easy to change it requires to patch the django framework while ideally one would be able plug in in its own reversal mechanism. In my enthusiasm I wrote a patch to the url-reversal system (http://code.djangoproject.com/ticket/2615) (with an example tag), but i realize its lacking (python 2.4 features, inefficient an sloppy.. but no matter, i noted the url reversal mechanism has had a patch as well lately (http://code.djangoproject.com/ticket/2977), and before we can start hacking again, it seems wise to wait in what direction the url-resolving issue will evolve. (I hope for a more open and pluggable approach) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
