tree 6dfc1110a7651ffc2926487d6e31b74fa45c9abb
parent 6cd3b812c0bb5c956d8264aae0ffdd94bbd52314
author Paul J. Davis <paul.joseph.davis@gmail.com> 1363665089 -0500
committer Robert Newson <rnewson@apache.org> 1406134577 +0100

[1/3] Start a rexi_server per remote node

This is part of a multi-release upgrade to switch to using a rexi_server
instance per remote node. The first commit introduces the new
rexi_server instances, the second switches to using the new instances
and the third will remove the singleton rexi_server. Each of these
commits should be in a separate release.

The new pattern introduced by this commit will start a 'rexi_server_%b'
process where the '%b' is replaced by the `erlang:phash2(Node)` for
which it will service requests. After the second commit is release each
rexi generated message will be sent to the rexi_server instance on the
remote node handling requests for the local node. The
`rexi_utils:server_pid/1` function is used to generate the id of the
remote server.