On Jul 29, 10:19 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Reverse URL construction (especially w.r.t things like HTTP
> redirects) is the big missing part.
We obviously need some way to get the SCRIPT_NAME from request to the
reverse resolver. Can we rely on SCRIPT_NAME remaining a constant for
handler instance?
If so, how about we just set it as a global cached var which the
resolver can look at, which would make the whole process transparent
to the end user.
If not, we'll need to tie the two together somehow (hence earlier
request.reverse(...) suggestion). We'd need to rethink the {% url %}
tag too...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
