web.py's session is based on utils.ThreadedDict, which provide a copy of variable for each thread, so it's thread safe. I got nothing wrong when I use the internal CherryPy server for development. Today, I tried almost a whole day to deploy an application with fastcgi and lighttpd to the production server, and I cann't do the user authorization anymore! I test and read the log, and I found that, there is only one Thread being used for different visitors! I used a processor to identify threads, and here is the log I got when I tried to visit the app from different computers.
2009-01-05 18:59:23,357 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> 2009-01-05 18:59:23,357 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> 2009-01-05 19:00:30,545 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> 2009-01-05 19:00:30,545 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> 2009-01-05 19:00:32,791 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> 2009-01-05 19:00:32,791 DEBUG [root] current thread is <_DummyThread(Dummy-6, started daemon)> as the log shows, only Dummy-6 thread used in that moment. It's rather strange! is there any one can figure out what wrong with it? and what should I do to use session in a fastcgi environment? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" 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/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
