<font face="courier new,monospace"><span class="Apple-style-span" style="font-family: arial; ">On Tue, Sep 14, 2010 at 3:46 PM, <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>></span> wrote:</span><br>
</font><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I'm not sure I understand this. What is a "Master-Slave" protocol? Why<br>
would someone not benefit from a Twisted-based implementation of such a<br>
protocol?</blockquote><div><br></div><div>OK I'm not sure either ;-) this is why I ask. But in my case I have the following</div><div>situation: behind my serial port I have a bus system made of me (the master)</div>
<div>and some slaves. The slaves are absolute passive until I send them a command.</div><div>After I've send a command to one of my slaves the salve ALWAY reply by sending</div><div>a packet.</div><div><br></div><div>
So what's the benefit if I have a "deamon thread" waiting the hole time to get</div><div>something from the serial line if the only time it can get something is immediately</div><div>after the master has send a packet? The communication is totally synchronous. </div>
<div><br></div><div>- Markus</div><div><br></div><div>-- </div></div>__________________________________________________________________<br><br>IMKO Micromodultechnik GmbH<br>Markus Hubig<br>System Administration & Development<br>
Im Stoeck 2<br>D-76275 Ettlingen / GERMANY<br><br>HR: HRB 360936 Amtsgericht Mannheim<br>President: Dipl.-Ing. (FH) Kurt Koehler<br><br>Tel: 0049-(0)7243-5921-26<br>Fax: 0049-(0)7243-5921-40<br>e-mail: <a href="mailto:mhubig@imko.de">mhubig@imko.de</a><br>
internet: <a href="http://www.imko.de">www.imko.de</a><br>_________________________________________________________________<br>