> > Even a little bit and You do the whole cloud software :] > > Interesting concept. You can practically do it already: > If the worker will overwrite its own configuration file will be restarted > with more or fewer workers. > Just transmit a message between servers. > > A little afraid that uWSGI getting too complicated. > I acknowledge the principle of KISS (keep it simple...). > And I'm not talking about a multitude of options available. >lman/listinfo/uwsgi
This is a fear for a lot of people. But hey, the new uWSGI is fully modular and i have already removed a lot of code from the core (for example the http server is a plugin in 0.9.7 as all the language support), and i have plan to make the core still thinnier for 0.9.8. (i will pluginize cache, queue [hint: this is an amazing undocumented feature, sorry guys], spooler, emperor and probably lot more) Having a solid (and simple) core will allow a better distribution of development resource too. Think about Lua and ruby support, they have the same functionality (+threading in Lua case) of python in uWSGI 0.9.4 in less than 700 lines of c code. >From now on, we can focus development in specific areas without messing with the other part of the server. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
