Andreas Rottmann 5bab8e85b9 Handle hup events as indicating read readiness ...

Using Linux's `epoll(7)` interface, a `EPOLLHUP` condition is
signalled for the reading end of a pipe or socket when the other end
is closed for writing. This may happen in combination with `EPOLLIN`
being signalled (if further data is available for reading), or with
`EPOLLIN`.

If `EPOLLHUP` is signalled without `EPOLLIN` it indicates an immediate
EOF condition, which will result in the next `read()` suceeding with 0
bytes read. It is thus not required to handle `EPOLLHUP` specially in
the reader, but we need to indicate readiness upon encountering it.

Looking at the `kqueue` and `windows` mio backends, they seem to be
turn a detected EOF and connection reset into `mio::Ready::hup()`
events, so it may be reasonable to speculate that this change is an
improvement for these platforms as well.

Fixes #117.

2016-12-08 17:52:40 +01:00

..

channel.rs

Reorganize the entire crate:

2016-09-07 22:12:14 -07:00

interval.rs

Implement tokio_core::reactor::Interval

2016-10-10 15:41:57 +03:00

io_token.rs

Swap Handle/Pinned

2016-09-07 22:12:41 -07:00

mod.rs

Handle hup events as indicating read readiness

2016-12-08 17:52:40 +01:00

poll_evented.rs

Add a method to manually deregister an I/O object

2016-11-04 09:12:00 -07:00

timeout_token.rs

Implement tokio_core::reactor::Interval

2016-10-10 15:41:57 +03:00

timeout.rs

Moves when to Timeout from TimeoutToken

2016-10-06 21:11:46 +03:00