Refactor gen_rpc, implement SSL support #63
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
gen_statem
tofollow Erlang's best practices
and development. As a result, support for Erlang releases older than
19.1 has been dropped.
off-heap mailboxes for client and acceptor,
and higher priorities for all
gen_rpc
processes.some research, offers no additional benefits
to having a static port listener. That means less processes to
supervise and less moving parts where something can
go wrong.
README for more information on
how to use it.
you to only make RPC calls to nodes that
run specific versions of modules.
lager
support has been dropped in favor of the loggingbackend-agnostic library
hut
, in order to better supportElixir installations. The test suite and development profiles still
use lager but this doesn't interfere with production
deployments of
gen_rpc
.functionality.
gen_rpc.app.src
have changed names to betterdescribe what they do. Again, pleaserefer to the README to
verify your preexisting settings are consistent with their new names.
massaged for consistency.