<div><br></div><div>Yair,</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><i><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">It is correct that each connection to Spread also has a private group that can be used</span></i></div>
<div><i><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">to multicast a message directly to that connection (process). But some process has to send</span></i></div>
<div><i><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)">such messages specifically to that private group. Right?</span></i></div></blockquote><div><br></div>
<div>This was our issue. There were other clients sending messages to the private group of our "write" only client. These messages were never being read and spread would eventually disconnect the "write" only client after the buffer is exceeded.</div>
<div><br></div><div>Regards,</div><div>##Shawn</div><br><br><div class="gmail_quote">On Sun, Nov 11, 2012 at 5:40 PM, Yair Amir <span dir="ltr"><<a href="mailto:yairamir@cs.jhu.edu" target="_blank">yairamir@cs.jhu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2au">It is correct that each connection to Spread also has a private group that can be used<br>
to multicast a message directly to that connection (process). But some process has to send<br>
such messages specifically to that private group. Right?</div></blockquote></div><br>