> ...but we've given some thought to putting the > get_absolute_url() logic in URLconfs instead, so at least the > logic is in a single file.
I'm not as concerned with where it's encapsulated, just that it is. I didn't know about the get_absolute_url() method and the ABSOLUTE_URL_OVERRIDES mentioned earlier in the thread. I'll be sure to check them out. I think the real goal I was aspiring to was protecting one application from another, i.e., having a sane way to cross link applications and protect others from my changes. The only issue I have with the model holding the URLs would be that an application's URLs are not always oriented around one particular model. So you're not really covered in, say, a wizard workflow. Anyway, back to slinging Java for another 8 hours. w00t! doug. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
