On Tue, Sep 12, 2017 at 03:37:43AM -0400, Frediano Ziglio wrote:
> >
> > On Mon, Sep 11, 2017 at 04:03:18AM -0400, Frediano Ziglio wrote:
> > > ping
> > >
> > > >
> > > > When the worker is started it could take a while to start
> > > > processing commands.
> > > > The reason is that the
>
> On Mon, Sep 11, 2017 at 04:03:18AM -0400, Frediano Ziglio wrote:
> > ping
> >
> > >
> > > When the worker is started it could take a while to start
> > > processing commands.
> > > The reason is that the dispatcher handler is called after
> > > the worker so GLib will receive a FALSE answer
On Mon, Sep 11, 2017 at 04:03:18AM -0400, Frediano Ziglio wrote:
> ping
>
> >
> > When the worker is started it could take a while to start
> > processing commands.
> > The reason is that the dispatcher handler is called after
> > the worker so GLib will receive a FALSE answer to both
> >
ping
>
> When the worker is started it could take a while to start
> processing commands.
> The reason is that the dispatcher handler is called after
> the worker so GLib will receive a FALSE answer to both
> prepare and check callbacks of the RedWorkerSource causing
> GLib to wait till another
When the worker is started it could take a while to start
processing commands.
The reason is that the dispatcher handler is called after
the worker so GLib will receive a FALSE answer to both
prepare and check callbacks of the RedWorkerSource causing
GLib to wait till another event is received.