summaryrefslogtreecommitdiff
path: root/qpid/doc/book/src/QmfIntroduction.xml
diff options
context:
space:
mode:
authorRajith Muditha Attapattu <rajith@apache.org>2011-05-27 15:44:23 +0000
committerRajith Muditha Attapattu <rajith@apache.org>2011-05-27 15:44:23 +0000
commit66765100f4257159622cefe57bed50125a5ad017 (patch)
treea88ee23bb194eb91f0ebb2d9b23ff423e3ea8e37 /qpid/doc/book/src/QmfIntroduction.xml
parent1aeaa7b16e5ce54f10c901d75c4d40f9f88b9db6 (diff)
parent88b98b2f4152ef59a671fad55a0d08338b6b78ca (diff)
downloadqpid-python-rajith_jms_client.tar.gz
Creating a branch for experimenting with some ideas for JMS client.rajith_jms_client
git-svn-id: https://svn.apache.org/repos/asf/qpid/branches/rajith_jms_client@1128369 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'qpid/doc/book/src/QmfIntroduction.xml')
-rw-r--r--qpid/doc/book/src/QmfIntroduction.xml45
1 files changed, 45 insertions, 0 deletions
diff --git a/qpid/doc/book/src/QmfIntroduction.xml b/qpid/doc/book/src/QmfIntroduction.xml
new file mode 100644
index 0000000000..db7b8949a5
--- /dev/null
+++ b/qpid/doc/book/src/QmfIntroduction.xml
@@ -0,0 +1,45 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+
+-->
+
+<chapter>
+<title>Introduction</title>
+
+<para>
+QMF enhances Qpid Messaging by providing a layer of functionality that makes it easy to implement common management patterns
+using messaging as the basis for communication. QMF consists of three primary parts:
+</para>
+
+<itemizedlist>
+ <listitem><para>
+A protocol definition defines conventions for the use of message addresses, message headers, and structured message bodies.
+ </para></listitem>
+
+ <listitem><para>
+A core QMF engine provides a C++ API and an implementation of a set of protocol handlers for QMF message communication.
+ </para></listitem>
+
+ <listitem><para>
+Bindings are provided that wrap the C++ API for use in other languages such as Python, Ruby, and .NET.
+ </para></listitem>
+</itemizedlist>
+
+</chapter>