50 lines
2.8 KiB
HTML
50 lines
2.8 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
|
||
|
|
<title>Module machi_chain_repair</title>
|
||
|
|
<link rel="stylesheet" type="text/css" href="stylesheet.css" title="EDoc">
|
||
|
|
</head>
|
||
|
|
<body bgcolor="white">
|
||
|
|
<div class="navbar"><a name="#navbar_top"></a><table width="100%" border="0" cellspacing="0" cellpadding="2" summary="navigation bar"><tr><td><a href="overview-summary.html" target="overviewFrame">Overview</a></td><td><a href="http://www.erlang.org/"><img src="erlang.png" align="right" border="0" alt="erlang logo"></a></td></tr></table></div>
|
||
|
|
<hr>
|
||
|
|
|
||
|
|
<h1>Module machi_chain_repair</h1>
|
||
|
|
<ul class="index"><li><a href="#description">Description</a></li><li><a href="#index">Function Index</a></li><li><a href="#functions">Function Details</a></li></ul>Erlang API for the Machi FLU TCP protocol version 1, with a
|
||
|
|
proxy-process style API for hiding messy details such as TCP
|
||
|
|
connection/disconnection with the remote Machi server.
|
||
|
|
|
||
|
|
|
||
|
|
<h2><a name="description">Description</a></h2><p>Erlang API for the Machi FLU TCP protocol version 1, with a
|
||
|
|
proxy-process style API for hiding messy details such as TCP
|
||
|
|
connection/disconnection with the remote Machi server.</p>
|
||
|
|
|
||
|
|
<p>Machi is intentionally avoiding using distributed Erlang for
|
||
|
|
Machi's communication. This design decision makes Erlang-side code
|
||
|
|
more difficult & complex, but it's the price to pay for some
|
||
|
|
language independence. Later in Machi's life cycle, we need to
|
||
|
|
(re-)implement some components in a non-Erlang/BEAM-based language.</p>
|
||
|
|
|
||
|
|
This module implements a "man in the middle" proxy between the
|
||
|
|
Erlang client and Machi server (which is on the "far side" of a TCP
|
||
|
|
connection to somewhere). This proxy process will always execute
|
||
|
|
on the same Erlang node as the Erlang client that uses it. The
|
||
|
|
proxy is intended to be a stable, long-lived process that survives
|
||
|
|
TCP communication problems with the remote server.
|
||
|
|
<h2><a name="index">Function Index</a></h2>
|
||
|
|
<table width="100%" border="1" cellspacing="0" cellpadding="2" summary="function index"><tr><td valign="top"><a href="#repair-7">repair/7</a></td><td></td></tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<h2><a name="functions">Function Details</a></h2>
|
||
|
|
|
||
|
|
<h3 class="function"><a name="repair-7">repair/7</a></h3>
|
||
|
|
<div class="spec">
|
||
|
|
<p><tt>repair(ConsistencyMode, Src, Repairing, UPI, MembersDict, ETS, Opts) -> any()</tt></p>
|
||
|
|
</div>
|
||
|
|
<hr>
|
||
|
|
|
||
|
|
<div class="navbar"><a name="#navbar_bottom"></a><table width="100%" border="0" cellspacing="0" cellpadding="2" summary="navigation bar"><tr><td><a href="overview-summary.html" target="overviewFrame">Overview</a></td><td><a href="http://www.erlang.org/"><img src="erlang.png" align="right" border="0" alt="erlang logo"></a></td></tr></table></div>
|
||
|
|
<p><i>Generated by EDoc, May 20 2015, 11:11:34.</i></p>
|
||
|
|
</body>
|
||
|
|
</html>
|