qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jonat...@apache.org
Subject svn commit: r1066676 [2/8] - in /qpid/site/docs/books/trunk: AMQP-Messaging-Broker-CPP-Book/html/ AMQP-Messaging-Broker-CPP-Book/pdf/ AMQP-Messaging-Broker-Java-Book/html/ AMQP-Messaging-Broker-Java-Book/pdf/ Programming-In-Apache-Qpid/html/ Programmin...
Date Wed, 02 Feb 2011 22:58:38 GMT
Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html Wed Feb  2 22:58:35 2011
@@ -1,4 +1,4 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.8. High Availability Messaging Clusters</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s07.html" title="1.7.  Queue State Replication"><link rel="next" href="ch01s09.html" title="1.9.  ACL"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.8. High Availability Messaging Clusters</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s07.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.8. High Availability Messaging Clusters</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s07.html" title="1.7.  Queue State Replication"><link rel="next" href="ch01s09.html" title="1.9.  AMQP compatibility"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.8. High Availability Messaging Clusters</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s07.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
     </th><td width="20%" align="right"> <a accesskey="n" href="ch01s09.html">Next</a></td></tr></table><hr></div><div class="section" title="1.8. High Availability Messaging Clusters"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="chap-Messaging_User_Guide-High_Availability_Messaging_Clusters"></a>1.8. High Availability Messaging Clusters</h2></div></div></div><p>
 		High Availability Messaging Clusters provide fault tolerance by ensuring that every broker in a <em class="firstterm">cluster</em> has the same queues, exchanges, messages, and bindings, and allowing a client to <em class="firstterm">fail over</em> to a new broker and continue without any loss of messages if the current broker fails or becomes unavailable. Because all brokers are automatically kept in a consistent state, clients can connect to and use any broker in a cluster. Any number of messaging brokers can be run as one <em class="firstterm">cluster</em>, and brokers can be added to or removed from a cluster while it is in use.
@@ -7,7 +7,7 @@
 	</p><p>
 		An OpenAIS daemon runs on every machine in the cluster, and these daemons communicate using multicast on a particular address. Every qpidd process in a cluster joins a named group that is automatically synchronized using OpenAIS Closed Process Groups (CPG) &#8212; the qpidd processes multicast events to the named group, and CPG ensures that each qpidd process receives all the events in the same sequence. All members get an identical sequence of events, so they can all update their state consistently.
 	</p><p>
-		Two messaging brokers are in the same cluster if 
+		Two messaging brokers are in the same cluster if
 		</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
 					They run on hosts in the same OpenAIS cluster; that is, OpenAIS is configured with the same mcastaddr, mcastport and bindnetaddr, and
 				</p></li><li class="listitem"><p>
@@ -47,13 +47,13 @@ uidgid {
 				</p></li></ul></div><p>
 			The qpid log contains entries that record significant clustering events, e.g. when a broker becomes a member of a cluster, the membership of a cluster is changed, or an old journal is moved out of the way. For instance, the following message states that a broker has been added to a cluster as the first node:
 		</p><pre class="screen">
-2009-07-09 18:13:41 info 127.0.0.1:1410(READY) member update: 127.0.0.1:1410(member) 
+2009-07-09 18:13:41 info 127.0.0.1:1410(READY) member update: 127.0.0.1:1410(member)
 2009-07-09 18:13:41 notice 127.0.0.1:1410(READY) first in cluster
 </pre><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
 				If you are using SELinux, the qpidd process and OpenAIS must have the same SELinux context, or else SELinux must be set to permissive mode. If both qpidd and OpenAIS are run as services, they have the same SELinux context. If both OpenAIS and qpidd are run as user processes, they have the same SELinux context. If one is run as a service, and the other is run as a user process, they have different SELinux contexts.
 			</p></div><p>
 			The following options are available for clustering:
-		</p><div class="table"><a name="tabl-Messaging_User_Guide-Starting_a_Broker_in_a_Cluster-Options_for_High_Availability_Messaging_Cluster"></a><p class="title"><b>Table 1.3. Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
+		</p><div class="table"><a name="tabl-Messaging_User_Guide-Starting_a_Broker_in_a_Cluster-Options_for_High_Availability_Messaging_Cluster"></a><p class="title"><b>Table 1.8. Options for High Availability Messaging Cluster</b></p><div class="table-contents"><table summary="Options for High Availability Messaging Cluster" border="1"><colgroup><col align="left"><col align="left"></colgroup><thead><tr><th colspan="2" align="center">
 							Options for High Availability Messaging Cluster
 						</th></tr></thead><tbody><tr><td align="left">
 							<span class="command"><strong>--cluster-name <em class="replaceable"><code>NAME</code></em></strong></span>
@@ -66,13 +66,22 @@ uidgid {
 						</td></tr><tr><td align="left">
 							<span class="command"><strong>--cluster-url <em class="replaceable"><code>URL</code></em></strong></span>
 						</td><td align="left">
-							An AMQP URL containing the local address that the broker advertizes to clients for fail-over connections. This is different for each host. By default, all local addresses for the broker are advertized. You only need to set this if 
+							An AMQP URL containing the local address that the broker advertizes to clients for fail-over connections. This is different for each host. By default, all local addresses for the broker are advertized. You only need to set this if
 							<div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
 										Your host has more than one active network interface, and
 									</p></li><li class="listitem"><p>
 										You want to restrict client fail-over to a specific interface or interfaces.
 									</p></li></ol></div>
-							 Each broker in the cluster is specified using the form: <span class="command"><strong> url = ["amqp:"][ user ["/" password] "@" ] protocol_addr *("," protocol_addr) protocol_addr = tcp_addr / rmda_addr / ssl_addr / ... tcp_addr = ["tcp:"] host [":" port] rdma_addr = "rdma:" host [":" port] ssl_addr = "ssl:" host [":" port]</strong></span> In most cases, only one address is advertized, but more than one address can be specified in if the machine running the broker has more than one network interface card, and you want to allow clients to connect using multiple network interfaces. Use a comma delimiter (",") to separate brokers in the URL. Examples: 
+							<p>Each broker in the cluster is specified using the following form:</p>
+
+<pre class="programlisting">url = ["amqp:"][ user ["/" password] "@" ] protocol_addr
+         ("," protocol_addr)*
+protocol_addr = tcp_addr / rmda_addr / ssl_addr / ...
+tcp_addr = ["tcp:"] host [":" port]
+rdma_addr = "rdma:" host [":" port]
+ssl_addr = "ssl:" host [":" port]</pre>
+
+                            <p>In most cases, only one address is advertized, but more than one address can be specified in if the machine running the broker has more than one network interface card, and you want to allow clients to connect using multiple network interfaces. Use a comma delimiter (",") to separate brokers in the URL. Examples:</p>
 							<div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
 										<span class="command"><strong>amqp:tcp:192.168.1.103:5672</strong></span> advertizes a single address to the broker for failover.
 									</p></li><li class="listitem"><p>
@@ -86,7 +95,7 @@ uidgid {
 								CMAN protects against the "split-brain" condition, in which a network failure splits the cluster into two sub-clusters that cannot communicate with each other. When "split-brain" occurs, each of the sub-clusters can access shared resources without knowledge of the other sub-cluster, resulting in corrupted cluster integrity.
 							</p>
 							 <p>
-								To avoid "split-brain", CMAN uses the notion of a "quorum". If more than half the cluster nodes are active, the cluster has quorum and can act. If half (or fewer) nodes are active, the cluster does not have quorum, and all cluster activity is stopped. There are other ways to define the quorum for particular use cases (e.g. a cluster of only 2 members), see the <a class="ulink" href="http://sources.redhat.com/cluster/wiki" target="_top">CMAN Wiki</a> 
+								To avoid "split-brain", CMAN uses the notion of a "quorum". If more than half the cluster nodes are active, the cluster has quorum and can act. If half (or fewer) nodes are active, the cluster does not have quorum, and all cluster activity is stopped. There are other ways to define the quorum for particular use cases (e.g. a cluster of only 2 members), see the <a class="ulink" href="http://sources.redhat.com/cluster/wiki" target="_top">CMAN Wiki</a>
 for more detail.
 							</p>
 							 <p>
@@ -225,7 +234,7 @@ connectionfactory.qpidConnectionfactory 
  mv rhm rhm.bak
  cp -a _cluster.bak.&lt;nnnn&gt;/rhm .
 </pre></li><li class="step" title="Step 2"><p>
-						Mark the store as clean: 
+						Mark the store as clean:
 </p><pre class="screen">qpid-cluster-store -c &lt;data-dir&gt;</pre><p>
 
 					</p></li></ol></div><p>
@@ -235,5 +244,5 @@ connectionfactory.qpidConnectionfactory 
 			</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s07.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s09.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.7. 
     Queue State Replication
    </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.9. 
-      ACL
-  </td></tr></table></div></body></html>
+      AMQP compatibility
+    </td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html Wed Feb  2 22:58:35 2011
@@ -1,515 +1,391 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.9.  ACL</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s08.html" title="1.8. High Availability Messaging Clusters"><link rel="next" href="ch01s10.html" title="1.10.  AMQP compatibility"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.9. 
-      ACL
-  </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s08.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.9.  AMQP compatibility</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s08.html" title="1.8. High Availability Messaging Clusters"><link rel="next" href="ch01s10.html" title="1.10. Qpid Interoperability Documentation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.9. 
+      AMQP compatibility
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s08.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s10.html">Next</a></td></tr></table><hr></div><div class="section" title="1.9.  ACL"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="qpid_ACL"></a>1.9. 
-      ACL
-  </h2></div></div></div><div class="section" title="1.9.1.  v2 ACL file format for brokers"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLfileformatforbrokers"></a>1.9.1. 
-      v2 ACL file format for brokers
-    </h3></div></div></div><p>
-      This new ACL implementation has been designed for implementation
-      and interoperability on all Qpid brokers. It is currently
-      supported in the following brokers:
-    </p><div class="table"><a name="id2653947"></a><p class="title"><b>Table 1.4. ACL Support in Qpid Broker Versions</b></p><div class="table-contents"><table summary="ACL Support in Qpid Broker Versions" border="1"><colgroup><col><col></colgroup><thead><tr><th>
-                  Broker
-                </th><th>
-                  Version
-                </th></tr></thead><tbody><tr><td>
-                  C++
-                </td><td>
-                  M4 onward
-                </td></tr><tr><td>
-                  Java
-                </td><td>
-                  M5 anticipated
-                </td></tr></tbody></table></div></div><br class="table-break"><p>
-            Contents
-          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
-                <a class="xref" href="ch01s09.html#ACL-v2ACLfileformatforbrokers" title="1.9.1.  v2 ACL file format for brokers">Section 1.9.1, &#8220;
-      v2 ACL file format for brokers
-    &#8221;</a>
-              </p></li><li class="listitem"><p>
-                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-Specification" title="1.9.1.1.  Specification">Section 1.9.1.1, &#8220;
-            Specification
-          &#8221;</a>
-                  </p></li><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-Validation" title="1.9.1.2.  Validation">Section 1.9.1.2, &#8220;
-            Validation
-          &#8221;</a>
-                  </p></li><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-Examplefile-3A" title="1.9.1.3.  Example file:">Section 1.9.1.3, &#8220;
-            Example file:
-          &#8221;</a>
-                  </p></li></ul></div><p>
-              </p></li><li class="listitem"><p>
-                <a class="xref" href="ch01s09.html#ACL-DesignDocumentation" title="1.9.2.  Design Documentation">Section 1.9.2, &#8220;
-            Design Documentation
-          &#8221;</a>
-              </p></li><li class="listitem"><p>
-                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-MappingofACLtrapstoactionandtype" title="1.9.2.1.  Mapping of ACL traps to action and type">Section 1.9.2.1, &#8220;
-            Mapping of ACL
-            traps to action and type
-          &#8221;</a>
-                  </p></li></ul></div><p>
-              </p></li><li class="listitem"><p>
-                <a class="xref" href="ch01s09.html#ACL-v2ACLUserGuide" title="1.9.3.  v2 ACL User Guide">Section 1.9.3, &#8220;
-            v2 ACL User Guide
-          &#8221;</a>
-              </p></li><li class="listitem"><p>
-                </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-WritingGood-2FFastACL" title="1.9.3.1.  Writing Good/Fast ACL">Section 1.9.3.1, &#8220;
-            Writing Good/Fast ACL
-          &#8221;</a>
-                  </p></li><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-GettingACLtoLog" title="1.9.3.2.  Getting ACL to Log">Section 1.9.3.2, &#8220;
-            Getting ACL to Log
-          &#8221;</a>
-                  </p></li><li class="listitem"><p>
-                    <a class="xref" href="ch01s09.html#ACL-UserId-2FdomainsrunningwithCbroker" title="1.9.3.3.  User Id / domains running with C++ broker">Section 1.9.3.3, &#8220;
-            User Id /
-            domains running with C++ broker
-          &#8221;</a>
-                  </p></li></ul></div><p>
-              </p></li></ul></div><p>
-            
-          </p><div class="section" title="1.9.1.1.  Specification"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Specification"></a>1.9.1.1. 
-            Specification
-          </h4></div></div></div><p>
-             Notes on file formats
-          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A line starting with the character '#' will be considered a
-            comment, and are ignored.
-            </p></li><li class="listitem"><p>Since the '#' char (and others that are commonly used for
-            comments) are commonly found in routing keys and other AMQP
-            literals, it is simpler (for now) to hold off on allowing
-            trailing comments (ie comments in which everything following a
-            '#' is considered a comment). This could be reviewed later once
-            the rest of the format is finalized.
-            </p></li><li class="listitem"><p>Empty lines ("") and lines that contain only whitespace (any
-            combination of ' ', '\f', '\n', '\r', '\t', '\v') are ignored.
-            </p></li><li class="listitem"><p>All tokens are case sensitive. "name1" != "Name1" and
-            "create" != "CREATE".
-            </p></li><li class="listitem"><p>Group lists may be extended to the following line by
-            terminating the line with the '\' character. However, this may
-            only occur after the group name or any of the names following the
-            group name. Empty extension lines (ie just a '\' character) are
-            not permitted.
-              
-                </p><pre class="programlisting">
-# Examples of extending group lists using a trailing '\' character
-
-group group1 name1 name2 \
-             name3 name4 \
-             name5
-
-group group2 \
-             group1 \
-             name6
-
-# The following are illegal:
-
-# '\' must be after group name
-group \
-      group3 name7 name8
-
-# No empty extension lines
-group group4 name9 \
-                   \
-             name10
-</pre><p>
-              
-            </p></li><li class="listitem"><p>Additional whitespace (ie more than one whitespace char)
-            between and after tokens is ignored. However group and acl
-            definitions must start with "group" or "acl" respectively and
-            with no preceding whitespace.
-            </p></li><li class="listitem"><p>All acl rules are limited to a single line.
-            </p></li><li class="listitem"><p>Rules are interpreted from the top of the file down until the
-            name match is obtained; at which point processing stops.
-            </p></li><li class="listitem"><p>The keyword "all" is reserved, and matches all individuals,
-            groups and actions. It may be used in place of a group or
-            individual name and/or an action - eg "acl allow all all", "acl
-            deny all all" or "acl deny user1 all".
-            </p></li><li class="listitem"><p>The last line of the file (whether present or not) will be
-            assumed to be "acl deny all all". If present in the file, any
-            lines below this one are ignored.
-            </p></li><li class="listitem"><p>Names and group names may contain only a-z, A-Z, 0-9,
-            '-','_'.
-            </p></li><li class="listitem"><p>Rules must be preceded by any group definitions they may use;
-            any name not previously defined as a group will be assumed to be
-            that of an individual.
-            </p></li><li class="listitem"><p>ACL rules must have the following tokens in order on a single
-            line:
-              </p><div class="itemizedlist"><ul class="itemizedlist" type="circle"><li class="listitem"><p>The string literal "acl";
-                </p></li><li class="listitem"><p>The permission;
-                </p></li><li class="listitem"><p>The name of a single group or individual or the keyword
-                "all";
-                </p></li><li class="listitem"><p>The name of an action or the keyword "all";
-                </p></li><li class="listitem"><p>Optionally, a single object name or the keyword "all";
-                </p></li><li class="listitem"><p>If the object is present, then optionally one or more
-                property name-value pair(s) (in the form property=value).
-                </p></li></ul></div><p>
-            </p></li></ul></div><pre class="programlisting">
-user = username[@domain[/realm]]
-user-list = user1 user2 user3 ...
-group-name-list = group1 group2 group3 ...
-
-group &lt;group-name&gt; = [user-list] [group-name-list]
-
-
-permission = [allow|allow-log|deny|deny-log]
-action = [consume|publish|create|access|bind|unbind|delete|purge|update]
-object = [virtualhost|queue|exchange|broker|link|route|method]
-property = [name|durable|owner|routingkey|passive|autodelete|exclusive|type|alternate|queuename|schemapackage|schemaclass]
-
-acl permission {&lt;group-name&gt;|&lt;user-name&gt;|"all"} {action|"all"} [object|"all"] [property=&lt;property-value&gt;]
-</pre></div><div class="section" title="1.9.1.2.  Validation"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Validation"></a>1.9.1.2. 
-            Validation
-          </h4></div></div></div><p>
-            The new ACL file format needs to perform validation on the acl
-            rules. The validation should be performed depending on the set
-            value:
-          </p><p>
-            strict-acl-validation=none
-            The default setting should be 'warn'
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s10.html">Next</a></td></tr></table><hr></div><div class="section" title="1.9.  AMQP compatibility"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="AMQP-Compatibility"></a>1.9. 
+      AMQP compatibility
+    </h2></div></div></div><p>
+            Qpid provides the most complete and compatible implementation
+            of AMQP. And is the most aggressive in implementing the latest
+            version of the specification.
           </p><p>
-            On validation of this acl the following checks would be expected:
-          </p><pre class="programlisting">
-acl allow client publish routingkey=exampleQueue exchange=amq.direct
-</pre><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>The If the user 'client' cannot be found, if the
-            authentication mechanism cannot be queried then a 'user' value
-            should be added to the file.
-            </p></li><li class="listitem"><p>There is an exchange called 'amq.direct'
-            </p></li><li class="listitem"><p>There is a queue bound to 'exampleQueue' on 'amq.direct'
-            </p></li></ol></div><p>
-            Each of these checks that fail will result in a log statement
-            being generated.
+            There are two brokers:
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>C++ with support for AMQP 0-10</p></li><li class="listitem"><p>Java with support for AMQP 0-8 and 0-9 (0-10 planned)</p></li></ul></div><p>
+            There are client libraries for C++, Java (JMS), .Net (written in
+            C#), python and ruby.
+          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>All clients support 0-10 and interoperate with the C++
+            broker.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The JMS client supports 0-8, 0-9 and 0-10 and interoperates
+            with both brokers.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The python and ruby clients will also support all versions,
+            but the API is dynamically driven by the specification used and
+            so differs between versions. To work with the Java broker you
+            must use 0-8 or 0-9, to work with the C++ broker you must use
+            0-10.
+            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>There are two separate C# clients, one for 0-8 that
+            interoperates with the Java broker, one for 0-10 that
+            inteoperates with the C++ broker.
+            </p></li></ul></div><p>
+            QMF Management is supported in Ruby, Python, C++, and via QMan
+            for Java JMX &amp; WS-DM.
+          </p><div class="section" title="1.9.1.  AMQP Compatibility of Qpid releases:"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-AMQPCompatibilityofQpidreleases-3A"></a>1.9.1. 
+            AMQP
+            Compatibility of Qpid releases:
+          </h3></div></div></div><p>
+            Qpid implements the AMQP Specification, and as the specification
+            has progressed Qpid is keeping up with the updates. This means
+            that different Qpid versions support different versions of AMQP.
+            Here is a simple guide on what use.
           </p><p>
-            In the case of a fatal logging the full file will be validated
-            before the broker shuts down.
-          </p></div><div class="section" title="1.9.1.3.  Example file:"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Examplefile-3A"></a>1.9.1.3. 
-            Example file:
-          </h4></div></div></div><pre class="programlisting">
-
-# Some groups
-group admin ted@QPID martin@QPID
-group user-consume martin@QPID ted@QPID
-group group2 kim@QPID user-consume rob@QPID
-group publisher group2 \
-                tom@QPID andrew@QPID debbie@QPID
-
-# Some rules
-acl allow carlt@QPID create exchange name=carl.*
-acl deny rob@QPID create queue
-acl allow guest@QPID bind exchange name=amq.topic routingkey=stocks.ibm.#  owner=self
-acl allow user-consume create queue name=tmp.*
-
-acl allow publisher publish all durable=false
-acl allow publisher create queue name=RequestQueue
-acl allow consumer consume queue durable=true
-acl allow fred@QPID create all
-acl allow bob@QPID all queue
-acl allow admin all
-acl deny kim@QPID all
-acl allow all consume queue owner=self
-acl allow all bind exchange owner=self
-
-# Last (default) rule
-acl deny all all
-</pre></div></div><div class="section" title="1.9.2.  Design Documentation"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-DesignDocumentation"></a>1.9.2. 
-            Design Documentation
-          </h3></div></div></div><div class="section" title="1.9.2.1.  Mapping of ACL traps to action and type"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-MappingofACLtrapstoactionandtype"></a>1.9.2.1. 
-            Mapping of ACL
-            traps to action and type
-          </h4></div></div></div><p>
-            The C++ broker maps the ACL traps in the follow way for AMQP
-            0-10:
-            The Java broker currently only performs ACLs on the AMQP
-            connection not on management functions:
-          </p><div class="table"><a name="id2653684"></a><p class="title"><b>Table 1.5. Mapping ACL Traps</b></p><div class="table-contents"><table summary="Mapping ACL Traps" border="1"><colgroup><col><col><col><col><col></colgroup><thead><tr><th>
-                  Object
-                </th><th>
-                  Action
-                </th><th>
-                  Properties
-                </th><th>
-                  Trap C++
-                </th><th>
-                  Trap Java
-                </th></tr></thead><tbody><tr><td>
-                  Exchange
+            Here is a matrix that describes the different versions supported
+            by each release. The status symbols are interpreted as follows:
+          </p><div class="variablelist"><dl><dt><span class="term">Y</span></dt><dd><p>supported</p></dd><dt><span class="term">N</span></dt><dd><p>unsupported</p></dd><dt><span class="term">IP</span></dt><dd><p>in progress</p></dd><dt><span class="term">P</span></dt><dd><p>planned</p></dd></dl></div><div class="table"><a name="id2736108"></a><p class="title"><b>Table 1.9. AMQP Version Support by Qpid Release</b></p><div class="table-contents"><table summary="AMQP Version Support by Qpid Release" border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
+                  Component
                 </td><td>
-                  Create
+                  Spec
                 </td><td>
-                  name type alternate passive durable
+                   
                 </td><td>
-                  ExchangeHandlerImpl::declare
+                   
+                </td><td>
+                   
                 </td><td>
-                  ExchangeDeclareHandler
+                   
                 </td></tr><tr><td>
-                  Exchange
+                   
+                </td><td>
+                   
                 </td><td>
-                  Delete
+                  M2.1
                 </td><td>
-                  name
+                  M3
                 </td><td>
-                  ExchangeHandlerImpl::delete
+                  M4
                 </td><td>
-                  ExchangeDeleteHandler
+                  0.5
                 </td></tr><tr><td>
-                  Exchange
+                  java client
                 </td><td>
-                  Access
+                  0-10
                 </td><td>
-                  name
+                   
+                </td><td>
+                  Y
                 </td><td>
-                  ExchangeHandlerImpl::query
+                  Y
                 </td><td>
-
+                  Y
                 </td></tr><tr><td>
-                  Exchange
+                   
                 </td><td>
-                  Bind
+                  0-9
                 </td><td>
-                  name routingkey queuename owner
+                  Y
                 </td><td>
-                  ExchangeHandlerImpl::bind
+                  Y
                 </td><td>
-                  QueueBindHandler
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  Exchange
+                   
                 </td><td>
-                  Unbind
+                  0-8
                 </td><td>
-                  name routingkey
+                  Y
                 </td><td>
-                  ExchangeHandlerImpl::unbind
+                  Y
                 </td><td>
-                  ExchangeUnbindHandler
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  Exchange
+                  java broker
                 </td><td>
-                  Access
+                  0-10
                 </td><td>
-                  name queuename routingkey
+                   
                 </td><td>
-                  ExchangeHandlerImpl::bound
+                   
+                </td><td>
+                   
                 </td><td>
-                  
+                  P
                 </td></tr><tr><td>
-                  Exchange
+                   
+                </td><td>
+                  0-9
                 </td><td>
-                  Publish
+                  Y
                 </td><td>
-                  name routingKey
+                  Y
                 </td><td>
-                  SemanticState::route
+                  Y
                 </td><td>
-                  BasicPublishMethodHandler
+                  Y
                 </td></tr><tr><td>
-                  Queue
+                   
+                </td><td>
+                  0-8
                 </td><td>
-                  Access
+                  Y
                 </td><td>
-                  name
+                  Y
                 </td><td>
-                  QueueHandlerImpl::query
+                  Y
                 </td><td>
-                  
+                  Y
                 </td></tr><tr><td>
-                  Queue
+                  c++ client/broker
                 </td><td>
-                  Create
+                  0-10
                 </td><td>
-                  name alternate passive durable exclusive autodelete
+                   
+                </td><td>
+                  Y
                 </td><td>
-                  QueueHandlerImpl::declare
+                  Y
                 </td><td>
-                  QueueDeclareHandler
+                  Y
                 </td></tr><tr><td>
-                  Queue
+                   
                 </td><td>
-                  Purge
+                  0-9
                 </td><td>
-                  name
+                  Y
                 </td><td>
-                  QueueHandlerImpl::purge
+                   
+                </td><td>
+                   
                 </td><td>
-                  QueuePurgeHandler
+                   
                 </td></tr><tr><td>
-                  Queue
+                  python client
                 </td><td>
-                  Purge
+                  0-10
                 </td><td>
-                  name
+                   
+                </td><td>
+                  Y
                 </td><td>
-                  Management::Queue::purge
+                  Y
                 </td><td>
-                  
+                  Y
                 </td></tr><tr><td>
-                  Queue
+                   
                 </td><td>
-                  Delete
+                  0-9
                 </td><td>
-                  name
+                  Y
                 </td><td>
-                  QueueHandlerImpl::delete
+                  Y
                 </td><td>
-                  QueueDeleteHandler
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  Queue
+                   
                 </td><td>
-                  Consume
+                  0-8
                 </td><td>
-                  name (possibly add in future?)
+                  Y
                 </td><td>
-                  MessageHandlerImpl::subscribe
+                  Y
                 </td><td>
-                  BasicConsumeMethodHandler
-                  BasicGetMethodHandler
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  &lt;Object&gt;
+                  ruby client
                 </td><td>
-                  Update
+                  0-10
                 </td><td>
                    
                 </td><td>
-                  ManagementProperty::set
+                   
                 </td><td>
-                  
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  &lt;Object&gt;
+                   
                 </td><td>
-                  Access
+                  0-8
                 </td><td>
-                   
+                  Y
                 </td><td>
-                  ManagementProperty::read
+                  Y
                 </td><td>
-                  
+                  Y
+                </td><td>
+                  Y
                 </td></tr><tr><td>
-                  Link
+                  C# client
+                </td><td>
+                  0-10
                 </td><td>
-                  Create
+                   
                 </td><td>
                    
                 </td><td>
-                  Management::connect
+                  Y
                 </td><td>
-                  
+                  Y
                 </td></tr><tr><td>
-                  Route
+                   
+                </td><td>
+                  0-8
+                </td><td>
+                  Y
+                </td><td>
+                  Y
                 </td><td>
-                  Create
+                  Y
                 </td><td>
+                  Y
+                </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="1.9.2.  Interop table by AMQP specification version"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-InteroptablebyAMQPspecificationversion"></a>1.9.2. 
+            Interop
+            table by AMQP specification version
+          </h3></div></div></div><p>
+            Above table represented in another format.
+          </p><div class="table"><a name="id2716500"></a><p class="title"><b>Table 1.10. AMQP Version Support - alternate format</b></p><div class="table-contents"><table summary="AMQP Version Support - alternate format" border="1"><colgroup><col><col><col><col><col></colgroup><tbody><tr><td>
                    
                 </td><td>
-                  Management:: -createFederationRoute-
+                  release
                 </td><td>
-                  
+                  0-8
+                </td><td>
+                  0-9
+                </td><td>
+                  0-10
                 </td></tr><tr><td>
-                  Route
+                  java client
                 </td><td>
-                  Delete
+                  M3 M4 0.5
                 </td><td>
-                   
+                  Y
                 </td><td>
-                  Management:: -deleteFederationRoute-
+                  Y
                 </td><td>
-                  
+                  Y
                 </td></tr><tr><td>
-                  Virtualhost
+                  java client
                 </td><td>
-                  Access
+                  M2.1
                 </td><td>
-                  name
+                  Y
                 </td><td>
-                  TBD
+                  Y
                 </td><td>
-                  ConnectionOpenMethodHandler
-                </td></tr></tbody></table></div></div><br class="table-break"><p>
-            Management actions that are not explicitly given a name property
-            it will default the name property to management method name, if
-            the action is 'W' Action will be 'Update', if 'R' Action will be
-            'Access'.
-          </p><p>
-            for example, if the mgnt method 'joinCluster' was not mapped in
-            schema it will be mapped in ACL file as follows
-          </p><div class="table"><a name="id2655978"></a><p class="title"><b>Table 1.6. Mapping Management Actions to ACL</b></p><div class="table-contents"><table summary="Mapping Management Actions to ACL" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>
-                  Object
-                </th><th>
-                  Action
-                </th><th>
-                  Property
-                </th></tr></thead><tbody><tr><td>
-                  Broker
-                </td><td>
-                  Update
-                </td><td>
-                  name=joinCluster
-                </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section" title="1.9.3.  v2 ACL User Guide"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLUserGuide"></a>1.9.3. 
-            v2 ACL User Guide
-          </h3></div></div></div><div class="section" title="1.9.3.1.  Writing Good/Fast ACL"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-WritingGood-2FFastACL"></a>1.9.3.1. 
-            Writing Good/Fast ACL
-          </h4></div></div></div><p>
-            The file gets read top down and rule get passed based on the
-            first match. In the following example the first rule is a dead
-            rule. I.e. the second rule is wider than the first rule. DON'T do
-            this, it will force extra analysis, worst case if the parser does
-            not kill the dead rule you might get a false deny.
-          </p><pre class="programlisting">
-allow peter@QPID create queue name=tmp &lt;-- dead rule!!
-allow peter@QPID create queue
-deny all all
-</pre><p>
-            By default files end with
-          </p><pre class="programlisting">
-deny all all
-</pre><p>
-            the mode of the ACL engine can be swapped to be allow based by
-            putting the following at the end of the file
-          </p><pre class="programlisting">
-allow all all
-</pre><p>
-            Note that 'allow' based file will be a LOT faster for message
-            transfer. This is because the AMQP specification does not allow
-            for creating subscribes on publish, so the ACL is executed on
-            every message transfer. Also, ACL's rules using less properties
-            on publish will in general be faster.
-          </p></div><div class="section" title="1.9.3.2.  Getting ACL to Log"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-GettingACLtoLog"></a>1.9.3.2. 
-            Getting ACL to Log
-          </h4></div></div></div><p>
-            In order to get log messages from ACL actions use allow-log and
-            deny-log for example
-          </p><pre class="programlisting">
-allow-log john@QPID all all
-deny-log guest@QPID all all
-</pre></div><div class="section" title="1.9.3.3.  User Id / domains running with C++ broker"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-UserId-2FdomainsrunningwithCbroker"></a>1.9.3.3. 
-            User Id /
-            domains running with C++ broker
-          </h4></div></div></div><p>
-            The user-id used for ACL is taken from the connection user-id.
-            Thus in order to use ACL the broker authentication has to be
-            setup. i.e. (if --auth no is used in combination with ACL the
-            broker will deny everything)
-          </p><p>
-            The user id in the ACL file is of the form
-            &lt;user-id&gt;@&lt;domain&gt; The Domain is configured via the
-            SASL configuration for the broker, and the domain/realm for qpidd
-            is set using --realm and default to 'QPID'.
-          </p><p>
-            To load the ACL module use, load the acl module cmd line or via
-            the config file
-          </p><pre class="programlisting">
-./src/qpidd --load-module src/.libs/acl.so
-</pre><p>
-            The ACL plugin provides the following option '--acl-file'. If do
-            ACL file is supplied the broker will not enforce ACL. If an ACL
-            file name is supplied, and the file does not exist or is invalid
-            the broker will not start.
-          </p><pre class="programlisting">
-ACL Options:
-  --acl-file FILE       The policy file to load from, loaded from data dir
-</pre></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s08.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.8. High Availability Messaging Clusters </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.10. 
-      AMQP compatibility
-    </td></tr></table></div></body></html>
+                  N
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  P
+                </td></tr><tr><td>
+                  java broker
+                </td><td>
+                  M2.1
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  c++ client/broker
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  N
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  c++ client/broker
+                </td><td>
+                  M2.1
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  python client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td></tr><tr><td>
+                  python client
+                </td><td>
+                  M2.1
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  ruby client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  ruby client
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  Y
+                </td><td>
+                  P
+                </td></tr><tr><td>
+                  C# client
+                </td><td>
+                  M3 M4 0.5
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td><td>
+                  N
+                </td></tr><tr><td>
+                  C# client
+                </td><td>
+                  trunk
+                </td><td>
+                  Y
+                </td><td>
+                  N
+                </td><td>
+                  Y
+                </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s08.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s10.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.8. High Availability Messaging Clusters </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.10. Qpid Interoperability Documentation</td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html Wed Feb  2 22:58:35 2011
@@ -1,108 +1,71 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.10.  AMQP compatibility</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s09.html" title="1.9.  ACL"><link rel="next" href="ch01s11.html" title="1.11. Qpid Interoperability Documentation"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.10. 
-      AMQP compatibility
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s09.html">Prev</a> </td><th width="60%" align="center">Chapter 1.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.10. Qpid Interoperability Documentation</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch01.html" title="Chapter 1.  Running the AMQP Messaging Broker"><link rel="prev" href="ch01s09.html" title="1.9.  AMQP compatibility"><link rel="next" href="ch02.html" title="Chapter 2.  Managing the AMQP Messaging Broker"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">1.10. Qpid Interoperability Documentation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s09.html">Prev</a> </td><th width="60%" align="center">Chapter 1. 
       Running the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch01s11.html">Next</a></td></tr></table><hr></div><div class="section" title="1.10.  AMQP compatibility"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="AMQP-Compatibility"></a>1.10. 
-      AMQP compatibility
-    </h2></div></div></div><p>
-            Qpid provides the most complete and compatible implementation
-            of AMQP. And is the most aggressive in implementing the latest
-            version of the specification.
-          </p><p>
-            There are two brokers:
-          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>C++ with support for AMQP 0-10</p></li><li class="listitem"><p>Java with support for AMQP 0-8 and 0-9 (0-10 planned)</p></li></ul></div><p>
-            There are client libraries for C++, Java (JMS), .Net (written in
-            C#), python and ruby.
-          </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>All clients support 0-10 and interoperate with the C++
-            broker.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The JMS client supports 0-8, 0-9 and 0-10 and interoperates
-            with both brokers.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>The python and ruby clients will also support all versions,
-            but the API is dynamically driven by the specification used and
-            so differs between versions. To work with the Java broker you
-            must use 0-8 or 0-9, to work with the C++ broker you must use
-            0-10.
-            </p></li></ul></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>There are two separate C# clients, one for 0-8 that
-            interoperates with the Java broker, one for 0-10 that
-            inteoperates with the C++ broker.
-            </p></li></ul></div><p>
-            QMF Management is supported in Ruby, Python, C++, and via QMan
-            for Java JMX &amp; WS-DM.
-          </p><div class="section" title="1.10.1.  AMQP Compatibility of Qpid releases:"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-AMQPCompatibilityofQpidreleases-3A"></a>1.10.1. 
-            AMQP
-            Compatibility of Qpid releases:
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="section" title="1.10. Qpid Interoperability Documentation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation"></a>1.10. Qpid Interoperability Documentation</h2></div></div></div><p>
+            This page documents the various interoperable features of the
+            Qpid clients.
+          </p><div class="section" title="1.10.1.  SASL"><div class="titlepage"><div><div><h3 class="title"><a name="QpidInteroperabilityDocumentation-SASL"></a>1.10.1. 
+            SASL
           </h3></div></div></div><p>
-            Qpid implements the AMQP Specification, and as the specification
-            has progressed Qpid is keeping up with the updates. This means
-            that different Qpid versions support different versions of AMQP.
-            Here is a simple guide on what use.
+            
+          </p><div class="section" title="1.10.1.1.  Standard Mechanisms"><div class="titlepage"><div><div><h4 class="title"><a name="QpidInteroperabilityDocumentation-StandardMechanisms"></a>1.10.1.1. 
+            Standard
+            Mechanisms
+          </h4></div></div></div><p>
+            <a class="ulink" href="http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer#SASL_mechanisms" target="_top">http://en.wikipedia.org/wiki/Simple_Authentication_and_Security_Layer#SASL_mechanisms</a>
           </p><p>
-            Here is a matrix that describes the different versions supported
-            by each release. The status symbols are interpreted as follows:
-          </p><div class="variablelist"><dl><dt><span class="term">Y</span></dt><dd><p>supported</p></dd><dt><span class="term">N</span></dt><dd><p>unsupported</p></dd><dt><span class="term">IP</span></dt><dd><p>in progress</p></dd><dt><span class="term">P</span></dt><dd><p>planned</p></dd></dl></div><div class="table"><a name="id2654992"></a><p class="title"><b>Table 1.7. AMQP Version Support by Qpid Release</b></p><div class="table-contents"><table summary="AMQP Version Support by Qpid Release" border="1"><colgroup><col><col><col><col><col><col></colgroup><tbody><tr><td>
+            This table list the various SASL mechanisms that each component
+            supports. The version listed shows when this
+            functionality was added to the product.
+          </p><div class="table"><a name="id2746938"></a><p class="title"><b>Table 1.11. SASL Mechanism Support</b></p><div class="table-contents"><table summary="SASL Mechanism Support" border="1"><colgroup><col><col><col><col><col><col><col></colgroup><tbody><tr><td>
                   Component
                 </td><td>
-                  Spec
-                </td><td>
-                   
-                </td><td>
-                   
-                </td><td>
-                   
-                </td><td>
-                   
-                </td></tr><tr><td>
-                   
+                  ANONYMOUS
                 </td><td>
-                   
+                  CRAM-MD5
                 </td><td>
-                  M2.1
+                  DIGEST-MD5
                 </td><td>
-                  M3
+                  EXTERNAL
                 </td><td>
-                  M4
+                  GSSAPI/Kerberos
                 </td><td>
-                  0.5
+                  PLAIN
                 </td></tr><tr><td>
-                  java client
-                </td><td>
-                  0-10
-                </td><td>
-                   
+                  C++ Broker
                 </td><td>
-                  Y
+                  M3[<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-1">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
                 </td><td>
-                  Y
+                  M3[<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-1">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>,<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-2">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
                 </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-9
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-8
-                </td><td>
-                  Y
+                  M3[<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-1">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>,<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-2">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
                 </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
+                  M1
                 </td></tr><tr><td>
-                  java broker
+                  C++ Client
                 </td><td>
-                  0-10
+                  M3[<a class="xref" href="ch01s10.html#QpidInteroperabilityDocumentation-1">Section 1.10.1.1, &#8220;
+            Standard
+            Mechanisms
+          &#8221;</a>]
                 </td><td>
                    
                 </td><td>
@@ -110,284 +73,160 @@
                 </td><td>
                    
                 </td><td>
-                  P
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-9
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
+                  M1
                 </td></tr><tr><td>
-                   
-                </td><td>
-                  0-8
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr><tr><td>
-                  c++ client/broker
-                </td><td>
-                  0-10
+                  Java Broker
                 </td><td>
                    
                 </td><td>
-                  Y
-                </td><td>
-                  Y
+                  M1
                 </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-9
-                </td><td>
-                  Y
-                </td><td>
                    
                 </td><td>
                    
                 </td><td>
-                   
+                  M1
                 </td></tr><tr><td>
-                  python client
-                </td><td>
-                  0-10
+                  Java Client
                 </td><td>
                    
                 </td><td>
-                  Y
-                </td><td>
-                  Y
+                  M1
                 </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-9
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-8
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
+                   
                 </td><td>
-                  Y
+                  M1
                 </td></tr><tr><td>
-                  ruby client
+                  .Net Client
                 </td><td>
-                  0-10
+                  M2
                 </td><td>
-                   
+                  M2
                 </td><td>
-                   
+                  M2
                 </td><td>
-                  Y
+                  M2
                 </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-8
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
+                  M2
                 </td></tr><tr><td>
-                  C# client
-                </td><td>
-                  0-10
+                  Python Client
                 </td><td>
                    
                 </td><td>
                    
                 </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr><tr><td>
                    
                 </td><td>
-                  0-8
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr></tbody></table></div></div><br class="table-break"></div><div class="section" title="1.10.2.  Interop table by AMQP specification version"><div class="titlepage"><div><div><h3 class="title"><a name="AMQPcompatibility-InteroptablebyAMQPspecificationversion"></a>1.10.2. 
-            Interop
-            table by AMQP specification version
-          </h3></div></div></div><p>
-            Above table represented in another format.
-          </p><div class="table"><a name="id2656743"></a><p class="title"><b>Table 1.8. AMQP Version Support - alternate format</b></p><div class="table-contents"><table summary="AMQP Version Support - alternate format" border="1"><colgroup><col><col><col><col><col></colgroup><tbody><tr><td>
                    
                 </td><td>
-                  release
-                </td><td>
-                  0-8
-                </td><td>
-                  0-9
-                </td><td>
-                  0-10
-                </td></tr><tr><td>
-                  java client
-                </td><td>
-                  M3 M4 0.5
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td></tr><tr><td>
-                  java client
-                </td><td>
-                  M2.1
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  N
-                </td></tr><tr><td>
-                  java broker
-                </td><td>
-                  M3 M4 0.5
-                </td><td>
-                  Y
-                </td><td>
-                  Y
-                </td><td>
-                  N
-                </td></tr><tr><td>
-                  java broker
-                </td><td>
-                  trunk
-                </td><td>
-                  Y
-                </td><td>
-                  Y
+                   
                 </td><td>
-                  P
+                  ?
                 </td></tr><tr><td>
-                  java broker
+                  Ruby Client
                 </td><td>
-                  M2.1
+                   
                 </td><td>
-                  Y
+                   
                 </td><td>
-                  Y
+                   
                 </td><td>
-                  N
-                </td></tr><tr><td>
-                  c++ client/broker
+                   
                 </td><td>
-                  M3 M4 0.5
+                   
                 </td><td>
-                  N
+                  ?
+                </td></tr></tbody></table></div></div><br class="table-break"><p><a name="QpidInteroperabilityDocumentation-1"></a>        
+            1: Support for these will be in M3 (currently available on
+            trunk).
+	  </p><p><a name="QpidInteroperabilityDocumentation-2"></a>2: C++ Broker uses <a class="ulink" href="http://freshmeat.net/projects/cyrussasl/" target="_top">Cyrus SASL</a> which
+            supports CRAM-MD5 and GSSAPI but these have not been tested yet
+          </p></div><div class="section" title="1.10.1.2.  Custom Mechanisms"><div class="titlepage"><div><div><h4 class="title"><a name="QpidInteroperabilityDocumentation-CustomMechanisms"></a>1.10.1.2. 
+            Custom
+            Mechanisms
+          </h4></div></div></div><p>
+            There have been some custom mechanisms added to our
+            implementations.
+          </p><div class="table"><a name="id2744313"></a><p class="title"><b>Table 1.12. SASL Custom Mechanisms</b></p><div class="table-contents"><table summary="SASL Custom Mechanisms" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
+                  Component
                 </td><td>
-                  N
+                  AMQPLAIN
                 </td><td>
-                  Y
+                  CRAM-MD5-HASHED
                 </td></tr><tr><td>
-                  c++ client/broker
-                </td><td>
-                  M2.1
+                  C++ Broker
                 </td><td>
-                  N
-                </td><td>
-                  Y
+                   
                 </td><td>
-                  N
+                   
                 </td></tr><tr><td>
-                  python client
-                </td><td>
-                  M3 M4 0.5
+                  C++ Client
                 </td><td>
-                  Y
-                </td><td>
-                  Y
+                   
                 </td><td>
-                  Y
+                   
                 </td></tr><tr><td>
-                  python client
-                </td><td>
-                  M2.1
+                  Java Broker
                 </td><td>
-                  Y
+                  M1
                 </td><td>
-                  Y
-                </td><td>
-                  N
+                  M2
                 </td></tr><tr><td>
-                  ruby client
-                </td><td>
-                  M3 M4 0.5
+                  Java Client
                 </td><td>
-                  Y
+                  M1
                 </td><td>
-                  Y
-                </td><td>
-                  N
+                  M2
                 </td></tr><tr><td>
-                  ruby client
-                </td><td>
-                  trunk
+                  .Net Client
                 </td><td>
-                  Y
-                </td><td>
-                  Y
+                   
                 </td><td>
-                  P
+                   
                 </td></tr><tr><td>
-                  C# client
-                </td><td>
-                  M3 M4 0.5
+                  Python Client
                 </td><td>
-                  Y
+                  M2
                 </td><td>
-                  N
-                </td><td>
-                  N
+                   
                 </td></tr><tr><td>
-                  C# client
-                </td><td>
-                  trunk
-                </td><td>
-                  Y
+                  Ruby Client
                 </td><td>
-                  N
+                  M2
                 </td><td>
-                  Y
-                </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch01s11.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.9. 
-      ACL
-   </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 1.11. Qpid Interoperability Documentation</td></tr></table></div></body></html>
+                   
+                </td></tr></tbody></table></div></div><br class="table-break"><div class="section" title="1.10.1.2.1. AMQPLAIN"><div class="titlepage"><div><div><h5 class="title"><a name="id2750337"></a>1.10.1.2.1. AMQPLAIN</h5></div></div></div><p></p></div><div class="section" title="1.10.1.2.2. CRAM-MD5-HASHED"><div class="titlepage"><div><div><h5 class="title"><a name="id2766689"></a>1.10.1.2.2. CRAM-MD5-HASHED</h5></div></div></div><p>
+            The Java SASL implementations require that you have the password
+            of the user to validate the incoming request. This then means
+            that the user's password must be stored on disk. For this to be
+            secure either the broker must encrypt the password file or the
+            need for the password being stored must be removed.
+          </p><p>
+            The CRAM-MD5-HASHED SASL plugin removes the need for the plain
+            text password to be stored on disk. The mechanism defers all
+            functionality to the build in CRAM-MD5 module the only change is
+            on the client side where it generates the hash of the password
+            and uses that value as the password. This means that the Java
+            Broker only need store the password hash on the file system.
+            While a one way hash is not very secure compared to other forms
+            of encryption in environments where the having the password in
+            plain text is unacceptable this will provide and additional layer
+            to protect the password. In particular this offers some
+            protection where the same password may be shared amongst many
+            systems. It offers no real extra protection against attacks on
+            the broker (the secret is now the hash rather than the password).
+          </p></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s09.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.9. 
+      AMQP compatibility
+     </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. 
+      Managing the AMQP Messaging Broker
+    </td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02.html Wed Feb  2 22:58:35 2011
@@ -1,6 +1,6 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2.  Managing the AMQP Messaging Broker</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="prev" href="ch01s11.html" title="1.11. Qpid Interoperability Documentation"><link rel="next" href="ch02s02.html" title="2.2.  Qpid Management Framework"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2.             
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2.  Managing the AMQP Messaging Broker</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="prev" href="ch01s10.html" title="1.10. Qpid Interoperability Documentation"><link rel="next" href="ch02s02.html" title="2.2.  Qpid Management Framework"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. 
       Managing the AMQP Messaging Broker
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s11.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 2.  Managing the AMQP Messaging Broker"><div class="titlepage"><div><div><h2 class="title"><a name="chapter-Managing-CPP-Broker"></a>Chapter 2.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s10.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 2.  Managing the AMQP Messaging Broker"><div class="titlepage"><div><div><h2 class="title"><a name="chapter-Managing-CPP-Broker"></a>Chapter 2. 
       Managing the AMQP Messaging Broker
     </h2></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="section"><a href="ch02.html#section-Managing-CPP-Broker">2.1.  Managing the C++ Broker </a></span></dt><dd><dl><dt><span class="section"><a href="ch02.html#MgmtC-2B-2B-Usingqpidconfig">2.1.1. 
             Using qpid-config
@@ -442,6 +442,6 @@ Options:
   -h, --help  show this help message and exit
 </pre><p>
             You get the idea... have fun!
-          </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s11.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.11. Qpid Interoperability Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.2. 
+          </p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch01s10.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="ch02s02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">1.10. Qpid Interoperability Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.2. 
       Qpid Management Framework
     </td></tr></table></div></body></html>

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s02.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.2.  Qpid Management Framework</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch02.html" title="Chapter 2.  Managing the AMQP Messaging Broker"><link rel="prev" href="ch02.html" title="Chapter 2.  Managing the AMQP Messaging Broker"><link rel="next" href="ch02s03.html" title="2.3.  QMF Python Console Tutorial"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.2. 
       Qpid Management Framework
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><th width="60%" align="center">Chapter 2.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><th width="60%" align="center">Chapter 2. 
       Managing the AMQP Messaging Broker
-    </th><td width="20%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr></table><hr></div><div class="section" title="2.2.  Qpid Management Framework"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2649602"></a>2.2. 
+    </th><td width="20%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr></table><hr></div><div class="section" title="2.2.  Qpid Management Framework"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2716778"></a>2.2. 
       Qpid Management Framework
     </h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
                 <a class="xref" href="ch02s02.html#QpidManagementFramework-WhatIsQMF" title="2.2.1.  What Is QMF">Section 2.2.1, &#8220;
@@ -193,7 +193,7 @@
           </p><p>
             The XML syntax for &lt;property&gt; and &lt;statistic&gt; have
             the following XML-attributes:
-          </p><div class="table"><a name="id2658069"></a><p class="title"><b>Table 2.1. XML Attributes for QMF Properties and Statistics</b></p><div class="table-contents"><table summary="XML Attributes for QMF Properties and Statistics" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+          </p><div class="table"><a name="id2770835"></a><p class="title"><b>Table 2.1. XML Attributes for QMF Properties and Statistics</b></p><div class="table-contents"><table summary="XML Attributes for QMF Properties and Statistics" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
                   Attribute
                 </td><td>
                   &lt;property&gt;
@@ -329,7 +329,7 @@
             data types. The data types are based on the rich data typing
             system provided by the AMQP messaging protocol. The following
             table describes the data types available for QMF:
-          </p><div class="table"><a name="id2659619"></a><p class="title"><b>Table 2.2. QMF Datatypes</b></p><div class="table-contents"><table summary="QMF Datatypes" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
+          </p><div class="table"><a name="id2712703"></a><p class="title"><b>Table 2.2. QMF Datatypes</b></p><div class="table-contents"><table summary="QMF Datatypes" border="1"><colgroup><col><col></colgroup><tbody><tr><td>
                   QMF Type
                 </td><td>
                   Description
@@ -413,7 +413,7 @@
             attributes of different types. The following table enumerates the
             types available in the XML format, which QMF types they map to,
             and other special handling that occurs.
-          </p><div class="table"><a name="id2659894"></a><p class="title"><b>Table 2.3. XML Schema Mapping for QMF Types</b></p><div class="table-contents"><table summary="XML Schema Mapping for QMF Types" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
+          </p><div class="table"><a name="id2747576"></a><p class="title"><b>Table 2.3. XML Schema Mapping for QMF Types</b></p><div class="table-contents"><table summary="XML Schema Mapping for QMF Types" border="1"><colgroup><col><col><col><col></colgroup><tbody><tr><td>
                   XML Type
                 </td><td>
                   QMF Type
@@ -579,7 +579,7 @@
           </p></div><div class="section" title="2.2.6.  How to Write a QMF Agent"><div class="titlepage"><div><div><h3 class="title"><a name="QpidManagementFramework-HowtoWriteaQMFAgent"></a>2.2.6. 
             How to
             Write a QMF Agent
-          </h3></div></div></div><p></p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2.             
+          </h3></div></div></div><p></p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch02.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch02.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ch02s03.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. 
       Managing the AMQP Messaging Broker
      </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> 2.3. 
       QMF Python Console Tutorial

Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html?rev=1066676&r1=1066675&r2=1066676&view=diff
==============================================================================
--- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html (original)
+++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/ch02s03.html Wed Feb  2 22:58:35 2011
@@ -1,8 +1,8 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>2.3.  QMF Python Console Tutorial</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="AMQP Messaging Broker (Implemented in C++)"><link rel="up" href="ch02.html" title="Chapter 2.  Managing the AMQP Messaging Broker"><link rel="prev" href="ch02s02.html" title="2.2.  Qpid Management Framework"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">2.3. 
       QMF Python Console Tutorial
-    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s02.html">Prev</a> </td><th width="60%" align="center">Chapter 2.             
+    </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch02s02.html">Prev</a> </td><th width="60%" align="center">Chapter 2. 
       Managing the AMQP Messaging Broker
-    </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="section" title="2.3.  QMF Python Console Tutorial"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2652529"></a>2.3. 
+    </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="section" title="2.3.  QMF Python Console Tutorial"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2766130"></a>2.3. 
       QMF Python Console Tutorial
     </h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>
                 <a class="xref" href="ch02s03.html#QMFPythonConsoleTutorial-PrerequisiteInstallQpidMessaging" title="2.3.1.  Prerequisite - Install Qpid Messaging">Section 2.3.1, &#8220;
@@ -404,7 +404,7 @@ OK
             methods. Any number of these methods may be overridden by the
             console application. Any method that is not overridden defaults
             to a null handler which takes no action when invoked.
-          </p><div class="table"><a name="id2661193"></a><p class="title"><b>Table 2.4. QMF Python Console Class Methods</b></p><div class="table-contents"><table summary="QMF Python Console Class Methods" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
+          </p><div class="table"><a name="id2746071"></a><p class="title"><b>Table 2.4. QMF Python Console Class Methods</b></p><div class="table-contents"><table summary="QMF Python Console Class Methods" border="1"><colgroup><col><col><col></colgroup><tbody><tr><td>
                   Method
                 </td><td>
                   Arguments



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org


Mime
View raw message