<?xml version="1.0" encoding="windows-1252"?>
<node id="1020310" title="Re^3: Synchronising threads with signals (or not)" created="2013-02-23 09:41:46" updated="2013-02-23 09:41:46">
<type id="11">
note</type>
<author id="647953">
sundialsvc4</author>
<data>
<field name="doctext">
&lt;p&gt;
Obviously, that &lt;u&gt;was&lt;/u&gt; my question, and a very good question it was: &amp;nbsp; how is a music-recorder thread to be related to a music-player thread? &amp;nbsp; What are the two processes &lt;em&gt;doing&lt;/em&gt; together, such that they need to &lt;em&gt;sychronize?&lt;/em&gt; &amp;nbsp; A recorder certainly is a data-gatherer and a player is a data-consumer, but the two activities don&amp;rsquo;t particularly sound to me as something that would be synchronized in a producer/consumer relationship. &amp;nbsp; And &lt;em&gt;that&lt;/em&gt; is what has merely triggered idle speculation in both of us.
&lt;/p&gt;&lt;p&gt;
Subprocesses, such as &amp;ldquo;user-interface controls player and recorder threads,&amp;rdquo; are in my experience most-commonly handled with &lt;em&gt;signals&lt;/em&gt; to the effect that &amp;ldquo;your status has changed ... you need to do something differently now ... now wake up, or stop what you&amp;rsquo;re doing, and go find out what it is.&amp;rdquo; &amp;nbsp; Condition variables, on the other hand, are inherently a &lt;em&gt;synchronization&lt;/em&gt; mechanism. &amp;nbsp; Which is why I asked for clarification ... and perhaps also why the OP has now abandoned the question.
&lt;/p&gt;
</field>
<field name="root_node">
1020189</field>
<field name="parent_node">
1020228</field>
</data>
</node>
