Hi Roberto, I'm wondering how to improve the answer to the initial "what is uWSGI?" question, which I guess the point of the first sentence...
I wonder, if we had to answer it: - in one word? - in 3 or 4 words? - then, in a sentence? How would it look? Is it "uWSGI is a web application server"? Maybe that gets lost a bit in the description of it as a "stack for building clustered/distributed applications and network infrastructures"... So how about this kind of a rephrasing: "uWSGI is a better web application server. It is a highly modular, sysadmin-friendly, fully-featured stack for serving clustered and/or distributed applications." I was worried about the "network infrastructures" bit - it made me think - what, does it include switches, routers, and fibreoptic cables?? no) Hope that helps? I don't mean to be critical, just constructive... cheers, Harry > On Mon, 2012-11-26 at 08:52 +0100, Roberto De Ioris wrote: > I would like to change the description on the project homepage, to be > more-aligned with the current shape (and future directions) of the > project. > > I wrote that as a base (before committing i would like to have some > suggestion/opinion, and fix): > > uWSGI is an extremely advanced, sysadmin-friendly, highly-modular stack > for building clustered/distributed applications and network > infrastructures. > > The 'WSGI' part in the name is a tribute to the namesake standard for > python web applications, as it has been of inspiration for lot of > technologies and for lot of uWSGI plugins as well. > > Currently the uWSGI stack includes the following components: > > The core (implements configuration, processes management, sockets > creation, monitoring, logging, shared memory areas, ipc and > SubscriptionSystem) > > Request plugins (implement application server interfaces for various > languages and platforms: WSGI, PSGI, Rack, Lua WSAPI, CGI, PHP, Go ...) > > Gateways (implement load balancers, proxies and routers) > > The Emperor (implements massive instances management and monitoring) > > Loop engines (implement concurrency, currently uWSGI components can be run > in preforking, threaded, asynchronous/evented and green thread/coroutine > modes. Various forms of green threads/coroutines are supported, including > uGreen – uWSGI Green Threads, Greenlet, Stackless, The Gevent loop engine, > Goroutines and Fibers) > > Thanks to its pluggable architecture it can be extended without limits to > support more platforms and languages. Currently, you can write plugins in > C, C++ and Objective-C > > Sysadmins will love it as it can be configured via several methods, > including command line, environment variables, XML, INI, YAML, JSON, > SQLite and LDAP. > > To get started with uWSGI, take a look at the Installing uWSGI page. Then > continue to Quickstart or if you are feeling daring, the Configuration > Options page. Some example configurations are available on the Examples > page. > -- Harry Percival Developer [email protected] +44 (0) 20 3051 2751 PythonAnywhere - full python dev & hosting, in your browser 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK Harry Percival Developer [email protected] +44 (0) 20 3051 2751 PythonAnywhere - full python dev & hosting, in your browser 17a Clerkenwell Road, London EC1M 5RD, UK VAT No.: GB 893 5643 79 Registered in England and Wales as company number 5467329. Registered address: 843 Finchley Road, London NW11 8NA, UK _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
