Currently, call of any waiting method (`wait`, `waitAll` and so on) with zero timeout blocks execution until all required responses are received. That's not great because in some scenarios users want to check if there are any responses ready without blocking execution. Of course, one can use `wait(1)` which sleeps for only a millisecond, but anyway it's often unexpected that `wait(0)` sleeps forever. Let's stick to `epoll_wait` interface - `wait(0)` is non-blocking and `wait(-1)` blocks forever. Note that before the commit, passing `-1` would lead to an assertion failure. Note that we used to block forever in waiting methods by default. To maintain this behavior, the commit updates default value of timeout since the old default (zero) means non-blocking polling of connections now. Do not forget that `wait(0)` must poll connections - for this purpose, we should check if the timer has expired after the first call of `NetProvider.wait()`. The `timer.isExpired()` call actually protected us from calling `NetProvider.wait()` with negative timeout, and now it's gone, so let's replace `timer.elapsed()` method with new `timer.timeLeft()` which is more safe to use here (see tarantool#128 for details). Closes tarantool#111 Closes tarantool#128

wait(0) is actually wait(INFINITY) #111

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`wait(0)` is actually `wait(INFINITY)` #111