> Hi ... > > I have been looking into the documentation for more hints on the threads > part of uwsgi. I am planning on creating a C++ plugin for uwsgi and like > to know a little about how this will work while using the thread model. > > I really like the idea of not reinventing all the inner work of uwsgi (I > have done that before, but uwsgi have done a much better job) :-) > > I off cause need : > > enable-threads > > And I guess that this means that plugin will be loaded and I quess that > the "init" function will be executed ones (in the same startup thread as > when loading the plugin) ? > > All following requests are send using a thread per request, and I quess > they are all there are in a pool of threads defined by : > > threads=nn > > there are four stack size config entries ? > > thread-stacksize > threads-stacksize > thread-stack-size > threads-stack-size > > Do they all do the same ? > >
Hi, enable-threads is useful only if you need to embed something that needs to generate some special state for each process. Generally speaking, the wsgi_request structure is per-thread so, unless you need to hack on very specific parts of the uWSGI core you do not need locking. You may want to look at cutelyst (c++/QT): http://cutelyst.org/ that uses uWSGI as the serving core -- Roberto De Ioris http://unbit.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
