<html>
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Arial;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.Typed
{font-family:"Courier New";}
span.tty
{font-family:"Courier New";}
span.Name
{font-style:italic;}
span.Variable
{font-family:"Times New Roman";
font-style:italic;}
span.typed0
{font-family:"Courier New";}
span.name0
{font-style:italic;}
span.variable0
{font-family:"Times New Roman";
font-style:italic;}
span.emailstyle22
{font-family:Arial;
color:windowtext;}
span.EmailStyle27
{font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:navy'>I must admit, I am disappointed
that there is no Erlang solution. This seems like a basic building block
to fault-tolerant systems. So, I am going to toy with my idea of having
the secondary detect the failure and send the appropriate commands to the
network to redirect traffic for the primary server’s IP address to the
secondary. Am thinking there must be some DHCP commands to reassign the
IP address. Before I begin, does anyone see any obvious flaws in my
thinking. I am not a networking expert. Thanks.</span></p>
<p class=MsoNormal><span style='color:navy'> </span></p>
<p class=MsoNormal><span style='color:navy'>David</span></p>
<p class=MsoNormal><span style='color:navy'> </span></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'>
<hr size=2 width="100%" align=center tabindex=-1>
</div>
<p class=MsoNormal><b><span style='font-family:Tahoma'>From:</span></b><span
style='font-family:Tahoma'> David Mercer [mailto:dmercer@gmail.com] <br>
<b>Sent:</b> Friday, July 11, 2008 10:59<br>
<b>To:</b> 'erlang-questions@erlang.org'<br>
<b>Subject:</b> Fault-Tolerant TCP/IP Servers</span></p>
</div>
<p class=MsoNormal> </p>
<p class=MsoNormal>Say I have a TCP/IP server (e.g., a web server, FTP server, etc.)
written in Erlang, and I want it to work through hardware failures; I need at
least two of them. The problem is, clients are connecting to the
primary’s IP address, so when it fails, client connections are refused
instead of being rerouted to the secondary. What is the Erlang approach
to solving this?</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>My thought is that you have the secondary detect the failure
and send the appropriate commands to the network to redirect traffic for the
primary server’s IP address to the secondary. That’s my idea,
but I don’t really know if this is the appropriate solution, nor how to
implement something like this in Erlang.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>Please advise. Thank-you.</p>
<p class=MsoNormal> </p>
<p class=MsoNormal>David Mercer</p>
<p class=MsoNormal> </p>
<p class=MsoNormal> </p>
</div>
</div>
</body>
</html>