uloop assumes it is the main event loop. This fundamentally clashes
with openresty where the main event loop is the nginx one and for
obvious performance reasons all socket operations need to be done
through that one.
Dirk F.
On 15 June 2016 at 14:52, Anton K <a.ka...@gmail.com> wrote:
> Hello.
>
> I need to run one worker in infinite polling loop using ubus uloop (it use
> epoll_pwait on ubus socket). Same time, I need other workers (threads) doing
> some periodic tasks (timer-based, doing block operation – ioctl's on dev,
> something very similar to healthcheck but spending a lot of time on ioctls)
> and other workers accepting requests via http or a stream.
>
> How it could be achieved?.
