Latest 1.9 before 2.0 (scheduled at December 30th 2013)
From now on, all of the releases will be -rc's (no new features will be added)
A document describing notes for upgrades from the (extremely obsolete) 1.2 and 1.4 versions is on work.
This release includes a new simplified plugins builder subsystem directly embedded in the uWSGI binary.
A page reporting third plugins is available: :doc:`ThirdPartyPlugins` (feel free to add yours)
And now....
Changelog [20131211]
- croak if the psgi streamer fails
- allows building coroae on raspberrypi
- do not wait for write availability until strictly required
- avoid segfault when async mode api is called without async mode
- fixed plain (without suspend engine) async mode
- do not spit errors on non x86 timerfd_create
- support timerfd_create/timerfd_settime on __arm__
Inernally when the first response body is sent, uWSGI check if response headers have been sent too, and eventually send them with an additional write() call.
This new optimizations allows uWSGI to send both headers and the first body chunk with single writev() syscall.
If the writev() returns with an incomplete write on the second vector, the system will fallback to simple write().
Before this patch every single websocket packet required to allocate a memory chunk.
This patch forces the reuse of a single dynamic buffer. For games this should result in a pretty good improvement in responsiveness.
The zeromq api (a single function indeed) has been removed. Each plugin rquiring zeromq cam simply call zmq_init() insteadd of uwsgi_zeromq_init().
The mongrel2 support has been moved to a 'mongrel2' plugin.
To pair uWSGI with mongrel2 the same options as before can be used, just remember to load (and build) the mongrel2 plugin
The shared area subsystem has been rewritten (it is incompatible with the old api as it requires a new argument as it now supports multiple memory areas).
Check updated docs: :doc:`SharedArea`
every error when reading and writing to/from the client will report current request's data.
This should simplify debugging a lot.
The uWSGI api has been extended to allow plugins to define their log-request vars.
Check: :doc:`LogFormat`
6 new request logging variables are available:
tmsecs: report the current unix time in milliseconds
tmicros: report the current unix time in microseconds
werr: report the number of write errors for the current request
rerr: report the number of read errors for the current request
ioerr: the sum of werr and rerr
var.XXX: report the context of the request var XXX (like var.PATH_INFO)
The symcall plugin has been improved to support mules and mountpoints.
To run a C function in a mule just specify it as --mule=foobar() when the mule finds an argument ending
with () it will consider it a function symbol.
This two non-blocking hooks adds new capabilities to the non-blocking system.
The first one allows to wait on two file descriptors with the same call (currently implemented only in plain async mode)
The second one is used to have a millisecond resolution sleep. (this is currently used only by the sharedarea waiting system)
You can now send websocket binary message. Just use uwsgi.websocket_send_binary() instead of uwsgi.websocket_send()
Sending 'S' to the master fifo, enable/disable the sending of subscription packets
this new custom hooks allows you to execute custom code in every mule:
[uwsgi]
hook-as-mule = exec:myscript.sh
...The chain reloading subsystem has been improved to take in account when a worker is really ready to accept() requests.
This specific state is announced to the Emperor too.
Check this article for more infos: http://uwsgi-docs.readthedocs.org/en/latest/articles/TheArtOfGracefulReloading.html
this option allows you to call specific C functions (in chains) after each request. While you should use the framework/interface features for this kind of job, sometimes it is not possibile to execute code after the logging phase. In such a case feel free to abuse this option.
Three new options allow the definition of custom error pages (html only):
--error-page-403 <file> add an error page (html) for managed 403 response
--error-page-404 <file> add an error page (html) for managed 404 response
--error-page-500 <file> add an error page (html) for managed 500 response
Building uWSGI plugins is now super easy:
uwsgi --build-plugin <directory>this option will create a sane environment based on the current binary (no need to fight with build profiles and #ifdef) and will build the plugin.
No external files (included uwsgi.h) are needed as the uWSGI binary embeds them.
- implement websockets and sharedarea support in Lua
- complete sharedarea api for CPython, Perl, Ruby and PyPy
- implement read2 and wait_milliseconds hook in all of the available loop engines
uWSGI 1.9.21 has been released on December 11th 2013 and can be downloaded at: