Does a Worker has to run the code in blocking mode ? when it resumes execution of the code, initially after deferring (delaying the execution of code) to the next tick of event-loop.

[fakharksa]

According to Mezzio documentation (Please, see link / Reference at the end): The issue with Swoole is this that ;

After deferring (delaying the execution of code) to the next tick to event-loop, when the code resumes executing (in next tick), the Worker has to run the code in blocking mode which is why Solutions have to rely on Message Queues.

Question-1:

Is my interpretation to their statement is correct ? If yes, then ...

Question-2:
"Is their statement is highlighting the issue correctly ?" If, the answer is "No, that is not complete information / solution ", then ...

Question-3:
Does not an Swoole's Asynchronous Task-worker (or a user-created Swoole Process through addProcess() ) fits in such scenarion ? so as to obviate (remove) the need of Message Queue, successfully ?

#Reference:

Long-running processes