On Fri, Oct 2, 2009 at 9:16 PM, adelaide_mike
<mike.ro...@internode.on.net> wrote:
>
> Hi
> In my app the user needs to drill down through a series of templates
> and their views to identify a house. We start with the city, then the
> street and finally the house, in each case chosen from a rendering of
> the possible values selected from the relevant database table.
>
> I have all this working nicely using request.session['insert value
> here'] as the tool for storing the choices as they are made.
>
> My question is: is there a better or more proper way?
>
> Mike
Mike,
The primary disadvantage of storing navigation state in the session,
or, for that mater,
in variables sent in a POST, is that, for example, a user emailing the
url to their spouse
("Hey, honey, look at this one!") isn't going to work. If you are
concerned about long
urls, you could always compress them and then uuencode the value and
use that in the
url. Better probably would be just use a database primary key for the url part.
Bill
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
