On 15.03.2017 14:28, Vitaliy T wrote: > On 15 March 2017 at 13:29, Evgeny Grin <k...@yandex.ru> wrote: > Thank you! > > Now suspend/resume working out of a box for both epoll & select for > MHD_USE_XXX_INTERNALLY.
Suspend/resume logic wasn't changed. They should work as before. > > The bad news, there is regression for > MHD_set_connection_option (connection, MHD_CONNECTION_OPTION_TIMEOUT, > timeout) > > Previously if a timeout was set to 0, that's means the infinite timeout. > But now, the infinite timeout is equals to INT_MAX due the > implementation MHD_epoll(). The last one uses new semantics. > The changes is not updated in the microhttpd.h file. Could you provide small code sample to demonstrate problems that you are trying to solve? What do you mean by "ifinite timeout is equals to INT_MAX due the implementation MHD_epoll()"? Where is new semantics used? What change should be document? Timeout logic is still the same. Zero means "no timeout", any other value means "idle timeout in seconds". -- Best Wishes, Evgeny Grin
