Hi, why not to implement this check in the beginning of your view and if it's required just redirect the url to the same view with correct details which will just pass initial check?
-- wbr, rush 05.09.13, 08:51, "KentH" <k...@khauser.net>": > > Hi, > > I've got an app where I'd like to partially process some URLs, and then > afterwards have django resume & dispatch. > > Consider the following example: url pattern matches > http://www.example.com/location/dept/some/other/info. > > In this example, the location can move (eg: dept relocated). And the dept > name can change. > > The obvious (to me) solution is to turn location/dept into a <<dept object>> > ( a non-trivial operation which handles relocations, > and stores canonical location/dept in session to prevent repeated lookups, > etc) and then process the rest of the url, passing a > "dept=dept" kwarg. But to do this, I need django to pick up & carry on > resolving, with a different URL_ROOT. > > Is this possible? > > Thanks. Kent > > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at http://groups.google.com/group/django-users. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
