I'm not sure how to fix your problem, but message events are like javascript events, they end up in a queue. If your worker is still processing the loop, the new message sits in the queue till the worker's free. Sorry I can't help more, I'm new to gears.
On Jul 7, 11:29 am, Sergio Viudes <[email protected]> wrote: > I wrote a worker that has a big loop. If I send a message to this > worker while loop is executing, it isn't readed until loop ends. I > need message can be readed while executing that loop. > > Anybody has any ideas? > > Thanks
