Consider edm::async()

[makortel]

PR #29141 uses mostly-sleeping threads to achieve "pseudo asynchronous" behavior with RPC API's that do not provide fully asynchronous API (thread does the remote calls, then blocks the thread to wait for response, and after waking up notifies the edm::WaitingTaskWithArenaHolder that the work is done). If the use such threads starts to spread (more classes, more modules), it could be beneficial to abstract that behavior.

In a sense std::async() does the job, except

• thread behavior is unspecified (create+join every time vs pool)
• returns a future with which one can either query the state, or block the calling thread
  • Concurrency TS adds continuation passing which is the behavior we want

One option would be to create edm::async() that uses a specific thread pool to minimize thread creation and joining, and continuation passing (e.g. requiring edm::WaitingTaskWithArenaHolder be passed around).

[cmsbuild]

A new Issue was created by @makortel Matti Kortelainen.

@Dr15Jones, @smuzaffar, @silviodonato, @makortel, @davidlange6, @fabiocos can you please review it and eventually sign/assign? Thanks.

cms-bot commands are listed here

[makortel]

assign core

[cmsbuild]

New categories assigned: core

@Dr15Jones,@smuzaffar,@makortel you have been requested to review this Pull request/Issue and eventually sign? Thanks

[fwyzard]

Would that need a Service to own the thread pool ?

[makortel]

I haven't managed to come up with a better solution than a Service or a singleton object for a "nice" API, and that is the part I don't like that much.

[makortel]

Implemented in #44901

[cmsbuild]

cms-bot internal usage

[makortel]

+core

[cmsbuild]

This issue is fully signed and ready to be closed.