<br><br><div class="gmail_quote">On Sun, Feb 24, 2013 at 11:23 AM, Sergey Gerasimov <span dir="ltr"><<a href="mailto:sergun@gmail.com" target="_blank">sergun@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="RU" link="blue" vlink="purple"><div><p class="MsoNormal"><span lang="EN-US">Hello to all!<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US">I’m using PB as communication protocol for components of my system.<u></u><u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">Components can be located locally on the only one machine or in distributed fashion. It depends on the config file.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US"><u></u> <u></u></span></p>
<p class="MsoNormal"><span lang="EN-US">At the moment all communications are implemented as callRemote calls. I would like to keep this unified way of communication but make inter-machine calls as efficient as possible. What is the best way to do that?</span></p>
</div></div></blockquote><div><br></div><div>When you say "locally", is it still different processes talking to each other? Talking over TCP loopback on the same machine is pretty efficient, and unlikely to be a bottleneck, so you don't necessarily have to do anything special.</div>
<div><br></div><div>-Itamar</div></div>