diff options
author | Ulf Wiger <ulf@feuerlabs.com> | 2016-01-29 20:18:41 +0100 |
---|---|---|
committer | Ulf Wiger <ulf@feuerlabs.com> | 2016-02-09 21:46:58 +0100 |
commit | f490d5a35ae1776f15b8e3a485b406797e838b87 (patch) | |
tree | 504f236d8106b4f27ef04d481c102290bf1918a1 /CONFIGURE.md | |
parent | 646154b32105811b1f34fc5612e87e694c56b522 (diff) | |
download | rvi_core-f490d5a35ae1776f15b8e3a485b406797e838b87.tar.gz |
moved files to subdirs, w.i.p. on fragmentation
Diffstat (limited to 'CONFIGURE.md')
-rw-r--r-- | CONFIGURE.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/CONFIGURE.md b/CONFIGURE.md index 1b848a5..9364ba3 100644 --- a/CONFIGURE.md +++ b/CONFIGURE.md @@ -596,23 +596,23 @@ external node address chapter: Communication between the RVi components can be either JSON-RPC or Erlang-internal gen\_server calls. - -JSON-RPC calls provide compatability with replacement components + +JSON-RPC calls provide compatibility with replacement components written in languages other than Erlang. gen\_server calls provide native erlang inter-process calls that are signficantly faster than JSON-RPC when transmitting large data volumes. - + If one or more of the RVI components are replaced with external components, use JSON-RPC by ```json_rpc_address``` for all components. - + If an all-native erlang system is configured, use gen\_server calls by configuring ```gen_server```. If both ```gen_server``` and ```json_rpc_address``` are specified, the gen\_server communicaiton path will be used for inter component communication. - + Please note that communication between two RVI nodes are not affected by this since data_link_bert_rpc will use the protocol and data links specified by the matching routing rule to communicate. See |