Coming from the world of apache-prefork and mod_perl, we're about to roll
out our first django application using
WSGIDaemonProcess our-appname processes=6 threads=15
and we're having some discussion about what the "threads=15" means for our
Python code. Is our Python code now multi-threaded? Do we now have to
worry about shared data and concurrency and locking and thread-safe C
libraries?
The wsgi documentation says "The aim of mod_wsgi is to implement a simple
to use Apache module which can host *any Python application* which supports
the Python WSGI interface," which seems to imply that there is nothing
special our code has to worry even though we're running with "threads=15",
but it doesn't say so explicitly.
Could someone explain what the programming model is here in terms that
would be comprehensible to someone coming from the single-threaded
apache-prefork world?
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/modwsgi/-/-NPphiHX5ZoJ.
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/modwsgi?hl=en.
