Ichthyostega
2535e1b554
...since the session loop will be notified on any change via the interface, adding a command will activate the loop, and the builder timeout is handled separately via the dirty state. So there is no need to spin around the loop in idle state. As a aside, timeout waiting on a condition variable can be intentional and should thus not be logged as an error automatically. It is up to the calling context to decide if a timeout constitutes an exceptional situation. It is always a trade-off performance vs. readability. Sometimes a single-threaded implementation of self-contained logic is preferable to a slightly more performant yet obscure implementation based on our threadpool and scheduler. |
||
|---|---|---|
| .. | ||
| application | ||
| backend | ||
| proc | ||
| DIR_INFO | ||