The domain isn't changing. It's just the path, so links that use absolute paths will break. In a way I get it - using relative urls is easy to break something if you need to move it. Also copy & paste becomes hard. Perhaps an APPNAME_URL in your request context would help?
Tim ^,^ 2008/9/16 Jarek Zgoda <[EMAIL PROTECTED]>: > > Wiadomość napisana w dniu 2008-09-16, o godz. 10:02, przez est: > >> >> Today, my boss came to me and asked: "Please move our django site from >> http://xxx.com/ to http://xxx.com/v2/"; >> >> It's killing me. Just image how huge mount of HTML source code to >> modify. >> >> I STRONGLY suggest django implement a 'project url' like asp.net, say >> >> <link rel="stylesheet" href="~/main.css" type="text/css" >> media="screen" /> >> >> where ~ always points to the current django project's top URL path. >> >> This little feature will not slow down django template rendering, >> right? > > Why bother? Use only paths in urls, either absolute and relative and > you are set. This way root (/) is not domain dependent (use sites > framework for settings domain name). > > -- > We read Knuth so you don't have to. - Tim Peters > > Jarek Zgoda, R&D, Redefine > [EMAIL PROTECTED] > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
