From 5e54c04b1c7d7d9676ae1fd6a7e536d7979e30cb Mon Sep 17 00:00:00 2001 From: Norman Feske Date: Fri, 26 Aug 2016 11:26:10 +0200 Subject: [PATCH] remote_rom: minor README tweaks --- src/proxy/remote_rom/README | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/src/proxy/remote_rom/README b/src/proxy/remote_rom/README index 07bfa60..d2517c7 100644 --- a/src/proxy/remote_rom/README +++ b/src/proxy/remote_rom/README @@ -8,25 +8,25 @@ the specified backend and provides a ROM service via local RPC. Backends -------- -The remote_rom can be compiled with one of multiple backends that use different session +The remote_rom can be compiled with one of multiple back ends that use different session interfaces or libraries to forward and receive the packets. By exchanging the backend, -we can also easily change the publication strategy (e.g. notification+polling vs. multicast). -Furthermore, a backend is responsible for access control and optionally allows the +we can also easily change the publication strategy (e.g., notification+polling vs. multicast). +Furthermore, a back end is responsible for access control and optionally allows the specification of a policy for this. :'nic_ip': - This backend uses a Nic_session to transmit network packets with IPv4 headers. + This back end uses a Nic_session to transmit network packets with IPv4 headers. Configuration ------------- -Both, the client and the server evaluate the node of their config. -The _name_ attribute specifies the ROMs module name. The node may -further contain a node that can be used to populate the ROM with a default +Both the client and the server evaluate the '' node of their config. +The _name_ attribute specifies the ROMs module name. The '' node may +further contain a '' node that can be used to populate the ROM with a default content. Example ~~~~~~~ For an example that illustrates the use of these components, please refer to the -_run/test-remote_rom_backend_nic.run_ script. +_run/remote_rom_backend_nic_ip.run_ script.