[LAD] timing the processing of queues between engine and ui threads?

[Paul Davis]

On Thu, Nov 3, 2011 at 7:29 PM, Iain Duncan <iainduncanlists at gmail.com> wrote:
> Further to the conversation about Python to C++ ( with many helpful
> responses, thanks everyone! ).
>
> For my particular case, no drop outs is critical, and I really really want
> to be able to run multiple UIs on lots of cheap machines talking to the same
> engine over something (osc I expect). So I'm ok with the fact that user
> input and requests for user interface updates may lag, as the queue is
> likely to be really busy sometimes. I'm imagining:

you're going to want at least 3 threads:

  1) inside the engine, something to handle requests from a UI that
cannot be done under RT constraints
         and route others that can into ...
  2) the engine thread
  3) some UI (not necessarily in the same process)