aboutsummaryrefslogtreecommitdiffstats
path: root/lib/mnesia/doc/src/Mnesia_chap8.xml
diff options
context:
space:
mode:
authorBjörn Gustavsson <[email protected]>2015-06-15 11:52:18 +0200
committerBjörn Gustavsson <[email protected]>2015-06-15 11:52:18 +0200
commit8ce0fd7fb870ee2bd02d97c77e009d409266573e (patch)
tree3a0cffcd4904b316e2b8a5ca7a81a1ca437ebf38 /lib/mnesia/doc/src/Mnesia_chap8.xml
parent7b96828d2fa6dd66f57029529037933913b398c4 (diff)
parent572323a87f3ed28ae2af42f32cbc745e35b95101 (diff)
downloadotp-8ce0fd7fb870ee2bd02d97c77e009d409266573e.tar.gz
otp-8ce0fd7fb870ee2bd02d97c77e009d409266573e.tar.bz2
otp-8ce0fd7fb870ee2bd02d97c77e009d409266573e.zip
Merge branch 'bjorn/mnesia/doc'
* bjorn/mnesia/doc: Update asn1 documentation
Diffstat (limited to 'lib/mnesia/doc/src/Mnesia_chap8.xml')
-rw-r--r--lib/mnesia/doc/src/Mnesia_chap8.xml31
1 files changed, 14 insertions, 17 deletions
diff --git a/lib/mnesia/doc/src/Mnesia_chap8.xml b/lib/mnesia/doc/src/Mnesia_chap8.xml
index d35dd0c539..55309177b1 100644
--- a/lib/mnesia/doc/src/Mnesia_chap8.xml
+++ b/lib/mnesia/doc/src/Mnesia_chap8.xml
@@ -21,7 +21,7 @@
</legalnotice>
- <title>Combining Mnesia with SNMP</title>
+ <title>Combine Mnesia with SNMP</title>
<prepared>Claes Wikstr&ouml;m, Hans Nilsson and H&aring;kan Mattsson</prepared>
<responsible></responsible>
<docno></docno>
@@ -33,32 +33,29 @@
</header>
<section>
- <title>Combining Mnesia and SNMP </title>
+ <title>Combine Mnesia and SNMP</title>
<p>Many telecommunications applications must be controlled and
reconfigured remotely. It is sometimes an advantage to perform
this remote control with an open protocol such as the Simple
Network Management Protocol (SNMP). The alternatives to this would
- be:
- </p>
+ be the following:</p>
<list type="bulleted">
- <item>Not being able to control the application remotely at all.
+ <item>Not being able to control the application remotely
</item>
- <item>Using a proprietary control protocol.
+ <item>Using a proprietary control protocol
</item>
- <item>Using a bridge which maps control messages in a
+ <item>Using a bridge that maps control messages in a
proprietary protocol to a standardized management protocol and
- vice versa.
+ conversely
</item>
</list>
- <p>All of these approaches have different advantages and
- disadvantages. Mnesia applications can easily be opened to the
- SNMP protocol. It is possible to establish a direct one-to-one
- mapping between Mnesia tables and SNMP tables. This
- means that a Mnesia table can be configured to be <em>both</em>
- a Mnesia table and an SNMP table. A number of functions to
- control this behavior are described in the Mnesia reference
- manual.
- </p>
+ <p>All these approaches have different advantages and
+ disadvantages. <c>Mnesia</c> applications can easily be opened to
+ the SNMP protocol. A direct 1-to-1 mapping can be established
+ between <c>Mnesia</c> tables and SNMP tables. This means
+ that a <c>Mnesia</c> table can be configured to be <em>both</em>
+ a <c>Mnesia</c> table and an SNMP table. A number of functions to
+ control this behavior are described in the Reference Manual.</p>
</section>
</chapter>