You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by jo...@apache.org on 2010/06/24 20:50:25 UTC
svn commit: r957678 [2/11] - in /qpid/site/docs/books:
0.5/AMQP-Messaging-Broker-CPP-Book/html/
0.5/AMQP-Messaging-Broker-CPP-Book/pdf/
0.6/AMQP-Messaging-Broker-CPP-Book/html/
0.6/AMQP-Messaging-Broker-CPP-Book/pdf/
0.7/AMQP-Messaging-Broker-CPP-Book/...
Modified: qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html?rev=957678&r1=957677&r2=957678&view=diff
==============================================================================
--- qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html (original)
+++ qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s08.html Thu Jun 24 18:50:21 2010
@@ -1,15 +1,15 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>8. Starting a cluster</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="7. Queue State Replication"><link rel="next" href="ch01s09.html" title="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">8.
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.8. Starting a cluster</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.
Starting a cluster
</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="8. Starting a cluster"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2914465"></a>8.
+ </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. Starting a cluster"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2900964"></a>1.8.
Starting a cluster
- </h2></div></div></div><div class="section" title="8.1. Running a Qpidd cluster"><div class="titlepage"><div><div><h3 class="title"><a name="Startingacluster-RunningaQpiddcluster"></a>8.1.
+ </h2></div></div></div><div class="section" title="1.8.1. Running a Qpidd cluster"><div class="titlepage"><div><div><h3 class="title"><a name="Startingacluster-RunningaQpiddcluster"></a>1.8.1.
Running a
Qpidd cluster
</h3></div></div></div><p>
There are several pre-requisites to running a qpidd cluster:
- </p><div class="section" title="8.1.1. Install and configure openais/corosync"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Installandconfigureopenais-2Fcorosync"></a>8.1.1.
+ </p><div class="section" title="1.8.1.1. Install and configure openais/corosync"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Installandconfigureopenais-2Fcorosync"></a>1.8.1.1.
Install
and configure openais/corosync
</h4></div></div></div><p>
@@ -63,14 +63,14 @@ inet addr:20.0.20.32 Bcast:20.0.20.255
</pre><p>
The bindnetaddr is the logical AND of the inet addr and mask
values, in the example above 20.0.20.0
- </p></div><div class="section" title="8.1.2. Open your firewall"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Openyourfirewall"></a>8.1.2.
+ </p></div><div class="section" title="1.8.1.2. Open your firewall"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Openyourfirewall"></a>1.8.1.2.
Open your
firewall
</h4></div></div></div><p>
In the above example file, I use mcastport 5405.
This implies that your firewall must allow UDP
protocol over port 5405, or that you disable the firewall
- </p></div><div class="section" title="8.1.3. Use the proper identity."><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Usetheproperidentity."></a>8.1.3.
+ </p></div><div class="section" title="1.8.1.3. Use the proper identity."><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Usetheproperidentity."></a>1.8.1.3.
Use the
proper identity.
</h4></div></div></div><p>
@@ -97,7 +97,7 @@ uidgid {
uid: qpid
gid: qpid
}
-</pre></div><div class="section" title="8.1.4. Starting a Cluster"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-StartingaCluster"></a>8.1.4.
+</pre></div><div class="section" title="1.8.1.4. Starting a Cluster"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-StartingaCluster"></a>1.8.1.4.
Starting a
Cluster
</h4></div></div></div><p>
@@ -117,7 +117,7 @@ qpidd -p5674 --cluster-name=MY_CLUSTER -
In a deployed system, cluster members will normally be on
different hosts but for development its useful to be able to
create a cluster on a single host.
- </p></div><div class="section" title="8.1.5. SELinux conflicts"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-SELinuxconflicts"></a>8.1.5.
+ </p></div><div class="section" title="1.8.1.5. SELinux conflicts"><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-SELinuxconflicts"></a>1.8.1.5.
SELinux conflicts
</h4></div></div></div><p>
Developers will often start openais/corosync as a service like
@@ -148,7 +148,7 @@ qpidd -p5674 --cluster-name=MY_CLUSTER -
Note that in a deployed system both openais/corosync and qpidd
should be started as services, in which case there is no problem
with SELinux running in enforcing mode.
- </p></div><div class="section" title="8.1.6. Troubleshooting checklist."><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Troubleshootingchecklist."></a>8.1.6.
+ </p></div><div class="section" title="1.8.1.6. Troubleshooting checklist."><div class="titlepage"><div><div><h4 class="title"><a name="Startingacluster-Troubleshootingchecklist."></a>1.8.1.6.
Troubleshooting
checklist.
</h4></div></div></div><p>
@@ -163,8 +163,8 @@ qpidd -p5674 --cluster-name=MY_CLUSTER -
3. Your firewall allows TCP on the ports used by qpidd.
4. If you're starting openais as a service but running qpidd
directly, ensure selinux is in permissive mode
- </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">7.
+ </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"> 9.
+ </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>
Modified: qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html?rev=957678&r1=957677&r2=957678&view=diff
==============================================================================
--- qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html (original)
+++ qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s09.html Thu Jun 24 18:50:21 2010
@@ -1,16 +1,16 @@
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>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="8. Starting a cluster"><link rel="next" href="ch02.html" title="Chapter 2. 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">9.
+<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. Starting a cluster"><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.
Running the AMQP Messaging Broker
- </th><td width="20%" align="right"> <a accesskey="n" href="ch02.html">Next</a></td></tr></table><hr></div><div class="section" title="9. ACL"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="qpid_ACL"></a>9.
+ </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="9.1. v2 ACL file format for brokers"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLfileformatforbrokers"></a>9.1.
+ </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="id2915541"></a><p class="title"><b>Table 1.2. 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>
+ </p><div class="table"><a name="id2900317"></a><p class="title"><b>Table 1.2. 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
@@ -25,56 +25,56 @@
</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="9.1. v2 ACL file format for brokers">Section 9.1, “
+ <a class="xref" href="ch01s09.html#ACL-v2ACLfileformatforbrokers" title="1.9.1. v2 ACL file format for brokers">Section 1.9.1, “
v2 ACL file format for brokers
”</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="9.1.1. Specification">Section 9.1.1, “
+ <a class="xref" href="ch01s09.html#ACL-Specification" title="1.9.1.1. Specification">Section 1.9.1.1, “
Specification
”</a>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-Validation" title="9.1.2. Validation">Section 9.1.2, “
+ <a class="xref" href="ch01s09.html#ACL-Validation" title="1.9.1.2. Validation">Section 1.9.1.2, “
Validation
”</a>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-Examplefile-3A" title="9.1.3. Example file:">Section 9.1.3, “
+ <a class="xref" href="ch01s09.html#ACL-Examplefile-3A" title="1.9.1.3. Example file:">Section 1.9.1.3, “
Example file:
”</a>
</p></li></ul></div><p>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-DesignDocumentation" title="9.2. Design Documentation">Section 9.2, “
+ <a class="xref" href="ch01s09.html#ACL-DesignDocumentation" title="1.9.2. Design Documentation">Section 1.9.2, “
Design Documentation
”</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="9.2.1. Mapping of ACL traps to action and type">Section 9.2.1, “
+ <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, “
Mapping of ACL
traps to action and type
”</a>
</p></li></ul></div><p>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-v2ACLUserGuide" title="9.3. v2 ACL User Guide">Section 9.3, “
+ <a class="xref" href="ch01s09.html#ACL-v2ACLUserGuide" title="1.9.3. v2 ACL User Guide">Section 1.9.3, “
v2 ACL User Guide
”</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="9.3.1. Writing Good/Fast ACL">Section 9.3.1, “
+ <a class="xref" href="ch01s09.html#ACL-WritingGood-2FFastACL" title="1.9.3.1. Writing Good/Fast ACL">Section 1.9.3.1, “
Writing Good/Fast ACL
”</a>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-GettingACLtoLog" title="9.3.2. Getting ACL to Log">Section 9.3.2, “
+ <a class="xref" href="ch01s09.html#ACL-GettingACLtoLog" title="1.9.3.2. Getting ACL to Log">Section 1.9.3.2, “
Getting ACL to Log
”</a>
</p></li><li class="listitem"><p>
- <a class="xref" href="ch01s09.html#ACL-UserId-2FdomainsrunningwithCbroker" title="9.3.3. User Id / domains running with C++ broker">Section 9.3.3, “
+ <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, “
User Id /
domains running with C++ broker
”</a>
</p></li></ul></div><p>
</p></li></ul></div><p>
- </p><div class="section" title="9.1.1. Specification"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Specification"></a>9.1.1.
+ </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
@@ -163,7 +163,7 @@ object = [virtualhost|queue|exchange|bro
property = [name|durable|owner|routingkey|passive|autodelete|exclusive|type|alternate|queuename|schemapackage|schemaclass]
acl permission {<group-name>|<user-name>|"all"} {action|"all"} [object|"all"] [property=<property-value>]
-</pre></div><div class="section" title="9.1.2. Validation"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Validation"></a>9.1.2.
+</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
@@ -187,7 +187,7 @@ acl allow client publish routingkey=exam
</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="9.1.3. Example file:"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-Examplefile-3A"></a>9.1.3.
+ </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">
@@ -216,9 +216,9 @@ acl allow all bind exchange owner=self
# Last (default) rule
acl deny all all
-</pre></div></div><div class="section" title="9.2. Design Documentation"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-DesignDocumentation"></a>9.2.
+</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="9.2.1. Mapping of ACL traps to action and type"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-MappingofACLtrapstoactionandtype"></a>9.2.1.
+ </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>
@@ -226,7 +226,7 @@ acl deny all all
0-10:
The Java broker currently only performs ACLs on the AMQP
connection not on management functions:
- </p><div class="table"><a name="id2916046"></a><p class="title"><b>Table 1.3. 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>
+ </p><div class="table"><a name="id2901990"></a><p class="title"><b>Table 1.3. 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
@@ -435,7 +435,7 @@ acl deny all all
</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="id2917552"></a><p class="title"><b>Table 1.4. 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>
+ </p><div class="table"><a name="id2903497"></a><p class="title"><b>Table 1.4. 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
@@ -447,9 +447,9 @@ acl deny all all
Update
</td><td>
name=joinCluster
- </td></tr></tbody></table></div></div><br class="table-break"></div></div><div class="section" title="9.3. v2 ACL User Guide"><div class="titlepage"><div><div><h3 class="title"><a name="ACL-v2ACLUserGuide"></a>9.3.
+ </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="9.3.1. Writing Good/Fast ACL"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-WritingGood-2FFastACL"></a>9.3.1.
+ </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
@@ -476,7 +476,7 @@ allow all all
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="9.3.2. Getting ACL to Log"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-GettingACLtoLog"></a>9.3.2.
+ </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
@@ -484,7 +484,7 @@ allow all all
</p><pre class="programlisting">
allow-log john@QPID all all
deny-log guest@QPID all all
-</pre></div><div class="section" title="9.3.3. User Id / domains running with C++ broker"><div class="titlepage"><div><div><h4 class="title"><a name="ACL-UserId-2FdomainsrunningwithCbroker"></a>9.3.3.
+</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>
@@ -510,8 +510,8 @@ deny-log guest@QPID all all
</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="ch02.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">8.
+</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.
Starting a cluster
- </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2.
+ </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>
Added: qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html?rev=957678&view=auto
==============================================================================
--- qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html (added)
+++ qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s10.html Thu Jun 24 18:50:21 2010
@@ -0,0 +1,395 @@
+<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.
+ 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 & 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:
+ </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>
+ 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="id2902192"></a><p class="title"><b>Table 1.5. 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>
+ Spec
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td></tr><tr><td>
+
+ </td><td>
+
+ </td><td>
+ M2.1
+ </td><td>
+ M3
+ </td><td>
+ M4
+ </td><td>
+ 0.5
+ </td></tr><tr><td>
+ java client
+ </td><td>
+ 0-10
+ </td><td>
+
+ </td><td>
+ Y
+ </td><td>
+ Y
+ </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
+ </td></tr><tr><td>
+ java broker
+ </td><td>
+ 0-10
+ </td><td>
+
+ </td><td>
+
+ </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
+ </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
+ </td><td>
+
+ </td><td>
+ Y
+ </td><td>
+ Y
+ </td><td>
+ Y
+ </td></tr><tr><td>
+
+ </td><td>
+ 0-9
+ </td><td>
+ Y
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td></tr><tr><td>
+ python client
+ </td><td>
+ 0-10
+ </td><td>
+
+ </td><td>
+ Y
+ </td><td>
+ Y
+ </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
+ </td></tr><tr><td>
+ ruby client
+ </td><td>
+ 0-10
+ </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><tr><td>
+ C# client
+ </td><td>
+ 0-10
+ </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="id2904261"></a><p class="title"><b>Table 1.6. 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
+ </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="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>
Added: qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html?rev=957678&view=auto
==============================================================================
--- qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html (added)
+++ qpid/site/docs/books/0.5/AMQP-Messaging-Broker-CPP-Book/html/ch01s11.html Thu Jun 24 18:50:21 2010
@@ -0,0 +1,238 @@
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>1.11. 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="ch01s10.html" title="1.10. 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.11.
+ Qpid Interoperability Documentation
+ </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch01s10.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="ch02.html">Next</a></td></tr></table><hr></div><div class="section" title="1.11. Qpid Interoperability Documentation"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2898110"></a>1.11.
+ Qpid Interoperability Documentation
+ </h2></div></div></div><div class="section" title="1.11.1. Qpid Interoperability Documentation"><div class="titlepage"><div><div><h3 class="title"><a name="QpidInteroperabilityDocumentation-QpidInteroperabilityDocumentation"></a>1.11.1.
+ Qpid Interoperability Documentation
+ </h3></div></div></div><p>
+ This page documents the various interoperable features of the
+ Qpid clients.
+ </p><div class="section" title="1.11.1.1. SASL"><div class="titlepage"><div><div><h4 class="title"><a name="QpidInteroperabilityDocumentation-SASL"></a>1.11.1.1.
+ SASL
+ </h4></div></div></div><p>
+
+ </p><div class="section" title="1.11.1.1.1. Standard Mechanisms"><div class="titlepage"><div><div><h5 class="title"><a name="QpidInteroperabilityDocumentation-StandardMechanisms"></a>1.11.1.1.1.
+ Standard
+ Mechanisms
+ </h5></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>
+ 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="id2904694"></a><p class="title"><b>Table 1.7. 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>
+ ANONYMOUS
+ </td><td>
+ CRAM-MD5
+ </td><td>
+ DIGEST-MD5
+ </td><td>
+ EXTERNAL
+ </td><td>
+ GSSAPI/Kerberos
+ </td><td>
+ PLAIN
+ </td></tr><tr><td>
+ C++ Broker
+ </td><td>
+ M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>]
+ </td><td>
+ M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>,<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-2">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>]
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>,<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-2">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>]
+ </td><td>
+ M1
+ </td></tr><tr><td>
+ C++ Client
+ </td><td>
+ M3[<a class="xref" href="ch01s11.html#QpidInteroperabilityDocumentation-1">Section 1.11.1.1.1, “
+ Standard
+ Mechanisms
+ ”</a>]
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ M1
+ </td></tr><tr><td>
+ Java Broker
+ </td><td>
+
+ </td><td>
+ M1
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ M1
+ </td></tr><tr><td>
+ Java Client
+ </td><td>
+
+ </td><td>
+ M1
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ M1
+ </td></tr><tr><td>
+ .Net Client
+ </td><td>
+ M2
+ </td><td>
+ M2
+ </td><td>
+ M2
+ </td><td>
+ M2
+ </td><td>
+
+ </td><td>
+ M2
+ </td></tr><tr><td>
+ Python Client
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ ?
+ </td></tr><tr><td>
+ Ruby Client
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+
+ </td><td>
+ ?
+ </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.11.1.1.2. Custom Mechanisms"><div class="titlepage"><div><div><h5 class="title"><a name="QpidInteroperabilityDocumentation-CustomMechanisms"></a>1.11.1.1.2.
+ Custom
+ Mechanisms
+ </h5></div></div></div><p>
+ There have been some custom mechanisms added to our
+ implementations.
+ </p><div class="table"><a name="id2903945"></a><p class="title"><b>Table 1.8. 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>
+ AMQPLAIN
+ </td><td>
+ CRAM-MD5-HASHED
+ </td></tr><tr><td>
+ C++ Broker
+ </td><td>
+
+ </td><td>
+
+ </td></tr><tr><td>
+ C++ Client
+ </td><td>
+
+ </td><td>
+
+ </td></tr><tr><td>
+ Java Broker
+ </td><td>
+ M1
+ </td><td>
+ M2
+ </td></tr><tr><td>
+ Java Client
+ </td><td>
+ M1
+ </td><td>
+ M2
+ </td></tr><tr><td>
+ .Net Client
+ </td><td>
+
+ </td><td>
+
+ </td></tr><tr><td>
+ Python Client
+ </td><td>
+ M2
+ </td><td>
+
+ </td></tr><tr><td>
+ Ruby Client
+ </td><td>
+ M2
+ </td><td>
+
+ </td></tr></tbody></table></div></div><br class="table-break"><div class="section" title="1.11.1.1.2.1. AMQPLAIN"><div class="titlepage"><div><div><h6 class="title"><a name="id2904097"></a>1.11.1.1.2.1. AMQPLAIN</h6></div></div></div><p></p></div><div class="section" title="1.11.1.1.2.2. CRAM-MD5-HASHED"><div class="titlepage"><div><div><h6 class="title"><a name="id2904106"></a>1.11.1.1.2.2. CRAM-MD5-HASHED</h6></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><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"><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.10.
+ 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>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:commits-subscribe@qpid.apache.org