LOL sorry I didn't mean programming threads, I mean't form threads, meaning people posting comments in forms about issues. I can see how that was miss understood. Honestly I am kind of liking the idea behind event based servers more then thread based.
On Tue, Apr 17, 2012 at 11:54 PM, Roberto De Ioris <[email protected]> wrote: > > > Thanks this is very helpful to know. I am building a system with nginx > and > > uwsgi to get the system running on that. I have been avoiding using uwsgi > > for anything serious because I have been seeing a lot of threads > reporting > > problems with it. > > ...and you will continue to see that :) > > Threads are hard to domate (in-fact most of the time you will go > multiprocess). The current (1.2) uWSGI threading implementation is pretty > solid (while 0.9.x are completely broken), but being an ultra-complex part > i am pretty sure more bugs will pop-up in the future. (and i have to > thanks Graham Dumpleton [author of mod_wsgi] for pointing me to better > directions) > > By the way, it is pretty strange you found 'threading' support a > uwsgi-blocker as very few (maybe 3-4, uWSGI included) production-grade > WSGI servers seriously supports them (with mod_wsgi having the better > implementation for sure). > > In addition to this, a little part of web-related popular libraries are > not thread-safe, that is why multithreading is not a "too much popular" > paradigm in python-hosting. > > > -- > Roberto De Ioris > http://unbit.it > -- -- Regards, Bruce Wade http://ca.linkedin.com/in/brucelwade http://www.wadecybertech.com http://www.fittraineronline.com - Fitness Personal Trainers Online http://www.warplydesigned.com
