[GitHub] [incubator-brpc] jamesge commented on issue #1164: why ExecutionQueue not designed as a polling mechanism?

[GitBox <gi...@apache.org>]

jamesge commented on issue #1164:
URL: https://github.com/apache/incubator-brpc/issues/1164#issuecomment-661950226


   ExecutionQueue is designed for running tasks (with dependencies) **in order**, and different ExecutionQueues run in parallel to make good use of CPU cores.  The polling version does not make sense because we're not subscribing "events" that are not controlled by us: the submitted tasks are just created by users, who can perfectly run the tasks one-by-one with a for-loop, without any other code. However, if one of the tasks blocks, the calling thread blocks. If you don't need this behavior, you need ExecutionQueue.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@brpc.apache.org
For additional commands, e-mail: dev-help@brpc.apache.org