On Mon, Dec 17, 2012 at 1:58 PM, Kevin Cole <dc.l...@gmail.com> wrote:
> On Mon, Dec 17, 2012 at 1:57 PM, Kevin Cole <dc.l...@gmail.com> wrote: > > > And here I'll display my ignorance about threading. I've done nothing > > specific to ask for threading. I wouldn't know how to thread even if I > > had a sewing machine. ;-) I'm using apache prefork with mod-wsgi. In > > testing, I go to the URL page first, which I had hoped would set the > > global variable like everywhere else that I set values for small > > handful of globals, and that going to the autoname URL after that > > would see the global I had set. > > s/I go to the URL page first/I go to the login page first/ > Mind you, I'm not certain that it's a threading issue. If this happens under runserver, it can't be threading because that's single threaded. Most of the deployment things I've seen default to some multi (process, actually) threading, though. Is it possible that fetch_names is returning something that times out somehow and then looks empty? You might try rendering type(direktorie) in both views. If it looks like a thing of some kind other than a list, then you might need to copy its parts in login, rather than saving it as is. -- 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.
