From 84adefa331c4159d432d22840663c38f155cd4c1 Mon Sep 17 00:00:00 2001
From: Erlang/OTP <otp@erlang.org>
Date: Fri, 20 Nov 2009 14:54:40 +0000
Subject: The R13B03 release.

---
 lib/mnesia/doc/src/Mnesia_chap8.xml | 64 +++++++++++++++++++++++++++++++++++++
 1 file changed, 64 insertions(+)
 create mode 100644 lib/mnesia/doc/src/Mnesia_chap8.xml

(limited to 'lib/mnesia/doc/src/Mnesia_chap8.xml')

diff --git a/lib/mnesia/doc/src/Mnesia_chap8.xml b/lib/mnesia/doc/src/Mnesia_chap8.xml
new file mode 100644
index 0000000000..3d2e23cf57
--- /dev/null
+++ b/lib/mnesia/doc/src/Mnesia_chap8.xml
@@ -0,0 +1,64 @@
+<?xml version="1.0" encoding="latin1" ?>
+<!DOCTYPE chapter SYSTEM "chapter.dtd">
+
+<chapter>
+  <header>
+    <copyright>
+      <year>1997</year><year>2009</year>
+      <holder>Ericsson AB. All Rights Reserved.</holder>
+    </copyright>
+    <legalnotice>
+      The contents of this file are subject to the Erlang Public License,
+      Version 1.1, (the "License"); you may not use this file except in
+      compliance with the License. You should have received a copy of the
+      Erlang Public License along with this software. If not, it can be
+      retrieved online at http://www.erlang.org/.
+    
+      Software distributed under the License is distributed on an "AS IS"
+      basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
+      the License for the specific language governing rights and limitations
+      under the License.
+    
+    </legalnotice>
+
+    <title>Combining Mnesia with SNMP</title>
+    <prepared>Claes Wikstr&ouml;m, Hans Nilsson and H&aring;kan Mattsson</prepared>
+    <responsible></responsible>
+    <docno></docno>
+    <approved></approved>
+    <checked></checked>
+    <date></date>
+    <rev></rev>
+    <file>Mnesia_chap8.xml</file>
+  </header>
+
+  <section>
+    <title>Combining 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>
+    <list type="bulleted">
+      <item>Not being able to control the application remotely at all.
+      </item>
+      <item>Using a proprietary control protocol.
+      </item>
+      <item>Using a bridge which maps control messages in a
+       proprietary protocol to a standardized management protocol and
+       vice versa. 
+      </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>
+  </section>
+</chapter>
+
-- 
cgit v1.2.3