Yes, actually it is! It's thread safe, because it binds variable to the current thread, but with CherryPy, I can say not. CherryPy WSGIServer use a thread pool, that means it will recruit some thread at start time, and later use these threads for the requests instead of create new ones. In web.py ThreadedDict, it doesn't clearn the variable it bound to. it can be a problem, for example, sessions. Am I wrong? I tried a whole day to debug the session problem, and I found that, if I run out of the thread in the threadpool, then each thread is 'dirty', and UserAuthentication processor don't work anymore. and I think it's caused by the thread pool of CherryPy
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
