summaryrefslogtreecommitdiff
path: root/qpid/doc/book/src/QmfIntroduction.xml
blob: db7b8949a5178f0471f40dcca1fe78cde346d7fe (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
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>