| Overview |  |
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.
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.
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.| repair/7 |
repair(ConsistencyMode, Src, Repairing, UPI, MembersDict, ETS, Opts) -> any()
Generated by EDoc, May 20 2015, 11:11:34.