Add release notes for 2.1.1
This commit is contained in:
parent
c5e19a045d
commit
ea25c04a9c
|
@ -4,6 +4,7 @@ Release notes
|
|||
.. toctree::
|
||||
:maxdepth: 2
|
||||
|
||||
releases/v2.1.1
|
||||
releases/v2.1.0
|
||||
releases/v2.0.0
|
||||
releases/v1.2.1
|
||||
|
|
|
@ -0,0 +1,29 @@
|
|||
What's new in Tornado 2.1.1
|
||||
===========================
|
||||
|
||||
Oct 4, 2011
|
||||
-----------
|
||||
|
||||
Bug fixes
|
||||
~~~~~~~~~
|
||||
|
||||
* Fixed handling of closed connections with the ``epoll`` (i.e. Linux)
|
||||
``IOLoop``. Previously, closed connections could be shut down too early,
|
||||
which most often manifested as "Stream is closed" exceptions in
|
||||
``SimpleAsyncHTTPClient``.
|
||||
* Fixed a case in which chunked responses could be closed prematurely,
|
||||
leading to truncated output.
|
||||
* ``IOStream.connect`` now reports errors more consistently via logging
|
||||
and the close callback (this affects e.g. connections to localhost
|
||||
on FreeBSD).
|
||||
* ``IOStream.read_bytes`` again accepts both ``int`` and ``long`` arguments.
|
||||
* ``PeriodicCallback`` no longer runs repeatedly when ``IOLoop`` iterations
|
||||
complete faster than the resolution of ``time.time()`` (mainly a problem
|
||||
on Windows).
|
||||
|
||||
Backwards-compatibility note
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
* Listening for ``IOLoop.ERROR`` alone is no longer sufficient for detecting
|
||||
closed connections on an otherwise unused socket. ``IOLoop.ERROR`` must
|
||||
always be used in combination with ``READ`` or ``WRITE``.
|
Loading…
Reference in New Issue