<div dir="ltr">On Thu, Jan 31, 2013 at 9:45 AM, joachim <span dir="ltr"><<a href="mailto:zoachien@securax.org" target="_blank">zoachien@securax.org</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div class="im">
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="gmail_quote">
<div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
></blockquote>
</div>
<div>If you have no NAT or dynamic IP in your network,
you can just remove the registration process and
assign to each peer its IP address.</div>
<span><font color="#888888">
<div><br>
</div>
</font></span></div>
</blockquote>
<div><br>
</div>
<div>This is the answer. If 100% availability is
critical, your IP addresses shouldn't be changing anyway,
so take the registration process out entirely. </div>
</div>
<br>
</div>
</div>
</blockquote></div>
This advice is not valid for android / iphones though.<br></div></blockquote><div><br></div><div style>That's absurd. Why would you use a battery-powered smartphone if you are trying to have 100% availability?</div>
<div style><br></div></div><div><br></div>-- <br>-Chris Harrington<br><div>ACSDi Office: 763.559.5800</div><div><div>Mobile Phone: 612.326.4248</div></div><div><br></div>
</div></div>