You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by tr...@apache.org on 2014/01/17 20:11:02 UTC
svn commit: r1559227 - in /qpid/site: docs/ docs/components/dispatch-router/
docs/releases/ docs/releases/qpid-dispatch-0.1/ input/
input/components/dispatch-router/ input/releases/
input/releases/qpid-dispatch-0.1/
Author: tross
Date: Fri Jan 17 19:11:01 2014
New Revision: 1559227
URL: http://svn.apache.org/r1559227
Log:
NO-JIRA - Added release content for Qpid Dispatch Router.
Added:
qpid/site/docs/releases/qpid-dispatch-0.1/
qpid/site/docs/releases/qpid-dispatch-0.1/amqp-mapping.html
qpid/site/docs/releases/qpid-dispatch-0.1/release-0.1.html
qpid/site/input/releases/qpid-dispatch-0.1/
qpid/site/input/releases/qpid-dispatch-0.1/amqp-mapping.md
qpid/site/input/releases/qpid-dispatch-0.1/release-0.1.md
Modified:
qpid/site/docs/components/dispatch-router/index.html
qpid/site/docs/index.html
qpid/site/docs/releases/index.html
qpid/site/docs/site.conf
qpid/site/input/components/dispatch-router/index.md
qpid/site/input/index.html
qpid/site/input/releases/index.md
qpid/site/input/site.conf
Modified: qpid/site/docs/components/dispatch-router/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch-router/index.html?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch-router/index.html (original)
+++ qpid/site/docs/components/dispatch-router/index.html Fri Jan 17 19:11:01 2014
@@ -58,13 +58,11 @@ and brokers.</p>
<tbody>
<tr><td><em>Platforms</em></td><td>Linux</td></tr>
<tr><td><em>AMQP versions</em></td><td>1.0</td></tr>
-<tr><td><em>Download</em></td><td><a href="http://people.apache.org/~tross/qpid-dispatch-0.1rc5/">http://people.apache.org/~tross/qpid-dispatch-0.1rc5/</a></td></tr>
+<tr><td><em>Download</em></td><td><a href="http://www.apache.org/dyn/closer.cgi/qpid/dispatch/0.1/qpid-dispatch-0.1.tar.gz">qpid-dispatch-0.1.tar.gz</a> [<a href="http://www.apache.org/dist/qpid/dispatch/0.1/qpid-dispatch-0.1.tar.gz.asc">PGP</a>]</td></tr>
<tr><td><em>Source location</em></td><td><a href="http://svn.apache.org/repos/asf/qpid/dispatch/trunk/">http://svn.apache.org/repos/asf/qpid/dispatch/trunk/</a></td></tr>
</tbody>
</table>
-<p><a href="release-0.1.html">What can you do with Qpid Dispatch 0.1?</a></p>
-
<h2 id="overview">Overview</h2>
<p>The Dispatch router is an AMQP router that provides advanced interconnect for AMQP.
@@ -114,12 +112,13 @@ involving a broker at all.</p>
</div>
-<h2 id="technical-details">Technical Details</h2>
+<h2 id="documentation">Documentation</h2>
<div class="two-column">
<ul>
-<li><a href="amqp-mapping.html">Usage of AMQP</a></li>
+<li><a href="http://qpid.apache.org/releases/qpid-dispatch-0.1/release-0.1.html">Initial Release Overview</a></li>
+<li><a href="http://qpid.apache.org/releases/qpid-dispatch-0.1/amqp-mapping.html">Usage of AMQP</a></li>
</ul>
</div>
Modified: qpid/site/docs/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/index.html?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/docs/index.html (original)
+++ qpid/site/docs/index.html Fri Jan 17 19:11:01 2014
@@ -79,6 +79,7 @@
<ul>
<li><a href="http://qpid.apache.org/components/java-broker/index.html">Java broker</a> - A pure-Java AMQP message broker</li>
<li><a href="http://qpid.apache.org/components/cpp-broker/index.html">C++ broker</a> - A native-code AMQP message broker</li>
+ <li><a href="http://qpid.apache.org/components/dispatch-router/index.html">Dispatch Router</a> - A lightweight AMQP message router</li>
<li>More about <a href="http://qpid.apache.org/components/index.html#servers-and-tools">Qpid servers and tools</a></li>
</ul>
</div>
Modified: qpid/site/docs/releases/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/index.html?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/docs/releases/index.html (original)
+++ qpid/site/docs/releases/index.html Fri Jan 17 19:11:01 2014
@@ -60,6 +60,7 @@ and the
<ul>
<li><a href="qpid-0.24/index.html">Qpid 0.24</a>, September 2013</li>
<li><a href="qpid-proton-0.6/index.html">Qpid Proton 0.6</a>, January 2014</li>
+<li><a href="qpid-dispatch-0.1/index.html">Qpid Dispatch 0.1</a>, January 2014</li>
</ul>
<h2 id="past-releases">Past releases</h2>
Added: qpid/site/docs/releases/qpid-dispatch-0.1/amqp-mapping.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-0.1/amqp-mapping.html?rev=1559227&view=auto
==============================================================================
--- qpid/site/docs/releases/qpid-dispatch-0.1/amqp-mapping.html (added)
+++ qpid/site/docs/releases/qpid-dispatch-0.1/amqp-mapping.html Fri Jan 17 19:11:01 2014
@@ -0,0 +1,180 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>Dispatch AMQP Mapping - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <link rel="stylesheet" href="http://qpid.apache.org/site.css" type="text/css"/>
+ <link rel="stylesheet" href="http://qpid.apache.org/pygments.css" type="text/css"/>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="http://qpid.apache.org/ie.css" type="text/css"/>
+ <![endif]-->
+ <script type="text/javascript" src="http://qpid.apache.org/site.js"></script>
+ </head>
+ <body>
+ <div id="content">
+ <div id="top">
+ <a id="search-link" href="http://qpid.apache.org/search.html"><img width="22" height="16" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABUAAAAQCAYAAAD52jQlAAABmklEQVQ4y2P4//8/A7UxpkBoAxtPaIMTb2hdKW9I/WLe0Pp2nrC6YO7IKnGyDOUObTAAGnIRiP9j4oZPQJxGkqF8YXWRQE2/oAY84Q1rmMETUpfOF9LQBBQ7jGTBaqIM5YyolgUq/gjWBDRMxK+MF10hX0hdNFwNAReDCaCidVBXbManGGowJCgCK4VxGgoEjDAX8IfWKBLyGlDdSajBfjgN5Q2tUYe68jExkQBMEd1g9SH1rTgN5Q+tc4UaepwYQ/lC6/Khhi7GaShPYIMY1NDPDA0NTARdGtYwD2JoXTGBiKp/DFIIdIU3PgOFohv4gOqegtQCM4QjXkOBOagOlj75QhuE8ETSfKT0+pontK5aMLScH6uhDGlprEDDzkENfsAdUueMrIgrokEKKLcRKg/KIKeRDP8IzsrAYMTMUcE1qgiDwfgtEO8H4tvIBgDVRIGzdFiDC9CCfUjZ+BtvSIMPRt4HuzisoQGo6CVa3v8O1LQJlPMwg6TWEpRpoOGcjbWUgmFw1g2r8+UOr9VncGhgIZjfQ0OZYWwAIBYjaUYze6wAAAAASUVORK5CYII="/></a>
+
+ <ul id="global-navigation">
+ <li><a id="logotype" href="http://qpid.apache.org/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="http://qpid.apache.org/download.html">Download</a></li>
+ <li><a href="http://qpid.apache.org/documentation.html">Documentation</a></li>
+ <li><a href="http://qpid.apache.org/discussion.html">Discussion</a></li>
+ <li><a href="http://qpid.apache.org/issues.html">Issues</a></li>
+ <li><a href="http://qpid.apache.org/source-code.html">Source Code</a></li>
+ <li><a href="http://qpid.apache.org/resources.html">More Resources</a></li>
+ </ul>
+ </div>
+ <div id="middle">
+ <ul id="path-navigation"><li><a href="http://qpid.apache.org/releases/index.html">Releases</a></li><li><a href="http://qpid.apache.org/releases/qpid-dispatch-0.1/index.html">Qpid Dispatch Router 0.1</a></li><li>Dispatch AMQP Mapping</li></ul>
+ <h1 id="dispatch-amqp-mapping">Dispatch AMQP Mapping</h1>
+
+<p>Dispatch Router is an AMQP router and as such, it provides extensions,
+codepoints, and semantics for routing over AMQP. This page documents
+the details of Dispatch Router's use of AMQP.</p>
+
+<h2 id="delivery-annotations">Delivery Annotations</h2>
+
+<p>The following Delivery Annotation fields are defined by Dispatch Router:</p>
+
+<table>
+<tbody>
+<tr><td><em>Field</em></td><td><em>Type</em></td><td><em>Description</em></td></tr>
+<tr><td><span style="white-space: nowrap;">x-opt-qd.ingress</span></td><td>string</td><td>The identity of the ingress router for a message-routed message. The ingress router is the first router encountered by a transiting message. The router will, if this field is present, leave it unaltered. If the field is not present, the router shall insert the field with its own identity.</td></tr>
+<tr><td><span style="white-space: nowrap;">x-opt-qd.trace</span></td><td>list of string</td><td>The list of routers through which this message-routed message has transited. If this field is not present, the router shall do nothing. If the field is present, the router shall append its own identity to the end of the list.</td></tr>
+<tr><td>x-opt-qd.to</td><td>string</td><td>To-Override for message-routed messages. If this field is present, the address in this field shall be used for routing in lieu of the <em>to</em> field in the message properties. A router may append, remove, or modify this annotation field depending on the policy in place for routing the message.</td></tr>
+</tbody>
+</table>
+
+<h2 id="sourcetarget-capabilities">Source/Target Capabilities</h2>
+
+<p>The following Capability values are used in Sources and Targets.</p>
+
+<table>
+<tbody>
+<tr><td><em>Capability</em></td><td><em>Description</em></td></tr>
+<tr><td>qd.router</td><td>This capability is added to sources and targets that are used for inter-router message exchange.</td></tr>
+</tbody>
+</table>
+
+<h2 id="addresses-and-address-formats">Addresses and Address Formats</h2>
+
+<p>The following AMQP addresses and address patterns are used within Dispatch Router.</p>
+
+<h3 id="address-patterns">Address Patterns</h3>
+
+<table>
+<tbody>
+<tr><td><em>Pattern</em></td><td><em>Description</em></td></tr>
+<tr><td>/_local/<addr></td><td>An address that references a locally attached endpoint. Messages using this address pattern shall not be routed over more than one link.</td></tr>
+<tr><td><span style="white-space: nowrap;">/_topo/<area>/<router>/<addr></span></td><td>An address that references an endpoint attached to a specific router node in the network topology. Messages with addresses that follow this pattern shall be routed along the shortest path to the specified router. Note that addresses of this form are a-priori routable in that the address itself contains enough information to route the message to its destination.</td></tr>
+<tr><td>/<addr></td><td>A mobile address. An address of this format represents an endpoint or a set of distinct endpoints that are attached to the network in arbitrary locations. It is the responsibility of the router network to determine which router nodes are valid destinations for mobile addresses.</td></tr>
+</tbody>
+</table>
+
+<h3 id="supported-addresses">Supported Addresses</h3>
+
+<table>
+<tbody>
+<tr><td><em>Address</em></td><td><em>Description</em></td></tr>
+<tr><td>/_local/$management</td><td>The management agent on the attached router/container. This address would be used by an endpoint that is a management client/console/tool wishing to access management data from the attached container.</td></tr>
+<tr><td><span style="white-space: nowrap;">/_topo/0/Router.E/agent</span></td><td>The management agent at Router.E in area 0. This address would be used by a management client wishing to access management data from a specific container that is reachable within the network.</td></tr>
+<tr><td>/_local/qdhello</td><td>The router entity in each of the connected routers. This address is used to communicate with neighbor routers and is exclusively for the HELLO discovery protocol.</td></tr>
+<tr><td>/_local/qdrouter</td><td>The router entity in each of the connected routers. This address is used by a router to communicate with other routers in the network.</td></tr>
+<tr><td><span style="white-space: nowrap;">/_topo/0/Router.E/qdxrouter</span></td><td>The router entity at the specifically indicated router. This address form is used by a router to communicate with a specific router that may or may not be a neighbor.</td></tr>
+</tbody>
+</table>
+
+<h2 id="implementation-of-the-amqp-management-specification">Implementation of the AMQP Management Specification</h2>
+
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant to a limited degree with the emerging AMQP Management specification. This section provides the details of what is supported and what is not and what is planned and what is not.</p>
+
+<p>Non-compliance occurs for one of the following reasons:</p>
+
+<ul>
+<li>Implementation of an optional feature is not planned</li>
+<li>Implementation is not complete as of the current time</li>
+<li>The specified operation is considered suboptimal or unimplementable. In all of these cases, an issue is pending with the AMQP Technical Committee.</li>
+</ul>
+
+<h3 id="compliance-matrix">Compliance Matrix</h3>
+
+<table>
+<tbody>
+<tr><td><em>Operation/Feature</em></td><td><em>Requirement</em></td><td><em>Supported</em></td><td><em>Remarks</em></td></tr>
+<tr><td>CREATE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>READ</td><td>Should</td><td>No</td><td>Not yet implemented</td></tr>
+<tr><td>UPDATE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>DELETE</td><td>Should</td><td>No</td><td>There are currently no Manageable Entities for which this is appropriate</td></tr>
+<tr><td>READALL</td><td>Should</td><td>No</td><td>A non-standard version of this operation is supported that retrieves data from all entities of a type. There is an outstanding issue raised with the AMQP Technical Committee to address this requirement.</td></tr>
+<tr><td>DISCOVER-NAMES</td><td>Should</td><td>No</td><td>Not yet implemented</td></tr>
+<tr><td>DISCOVER-TYPES</td><td>Should</td><td>Yes</td><td>There are no types that implement base types</td></tr>
+<tr><td>DISCOVER-OPERATIONS</td><td>Should</td><td>Yes</td><td></td></tr>
+<tr><td>DISCOVER-MGMT-NODES</td><td>Should</td><td>Yes</td><td>This operation yields the addresses of all of the router nodes in the known network</td></tr>
+<tr><td>REGISTER</td><td>May</td><td>Not Planned</td><td>The router has a specific way to discover peers that does not involve this operation</td></tr>
+<tr><td>DEREGISTER</td><td>May</td><td>Not Planned</td><td>The router has a specific way to discover peers that does not involve this operation</td></tr>
+</tbody>
+</table>
+
+<h3 id="manageable-entities">Manageable Entities</h3>
+
+<table>
+<tbody>
+<tr><td><em>Type Name</em></td><td><em>Description</em></td></tr>
+<tr><td>org.apache.qpid.dispatch.allocator</td><td>Per-type memory allocation statistics</td></tr>
+<tr><td>org.apache.qpid.dispatch.connection</td><td>Connections to the router's container</td></tr>
+<tr><td>org.apache.qpid.dispatch.container</td><td>General state and statistics for the AMQP container</td></tr>
+<tr><td>org.apache.qpid.dispatch.container.node_type</td><td>Description of registered node types</td></tr>
+<tr><td>org.apache.qpid.dispatch.container.node</td><td>Description of registered nodes in the container</td></tr>
+<tr><td>org.apache.qpid.dispatch.router</td><td>General state and statistics for the router node</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.link</td><td>Per-link state and statistics for links attached to the router node</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.node</td><td>Per-node state and statistics for remote router nodes in the known network</td></tr>
+<tr><td>org.apache.qpid.dispatch.router.address</td><td>Per-address state and statistics for addresses known to this router</td></tr>
+</tbody>
+</table>
+
+ </div>
+ <div id="bottom">
+ <ul id="apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="apache-feather" width="48" height="14" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAC4AAAAOCAYAAABQFS4BAAAFnElEQVRIx83S22ukdx3H8e/v8Pyew5xnsrMJSZNsmm4PW91uL5ZWhIK9EA/Fq8Uiite9EuzVFhbxoqvd7kWLVEWEuioqpQgVtmpFssZtabpR9xCb7uQwmexMspPM5JmZ5/w8v9/v64UtiCi2StX3X/CCz4fMz8w8vN5qLSGihnf7ypkzdw333Eeaq43f/G7xtRb8H0bOnz//+He/9cLjCHpZEfL9ZrN5+9wLL55GUJ/f2W7B3M+WnzZRfqmAukA0jgpVfu1NHF1dGHZ+abbnswVckP8T+Orq6tEwjJ5/9plvlv5wZflO1PriY6dOYcwKX6xWyli/uLUaRf2jdwRUTBGl+kL6PA5HlVGQ2zNVK7T0WlJhr1wW6hcvLizE/zU4IsLS0lKxVjv09dXVP3/5RxcuHNy4dn18/r77LCIKOBFN+XWds4uQcuEOCKOZOr6b8O6E0OV+AGUtVd+I99JS4ks3XWncgctqlv36qe+9dvVDh79Xo9E4ufzH61/b6e5/YnHxEvY7bYPGNs5Wj+s8q4GdY7TkR8gxFGNdATiZKifwyHTXBZnPqZR4EScq9aNQxfPkem8YvVPhxhu/Pch+9YM/LQw+NPgTp0/PVuzydxTwh6M4sk9gLrj51nZxhwWqPdwgeXFYVcQkpdqgRlbmDhI1z3sqsyjPp4GquSMSCIrTUUATJlJSSKMeCePJ7TTr5OTQrBsH7JAY9kDK3n504WK7/ebi2tr+fww/e/bcZ6rj489YljNj2zYUnv6x50VpXRoFFGmFL9QTKR2qtocbdDAI+HhlBkp0QumUkgckI/0q6OPuEHrlHFaTEea
TGHUA3MwzXXB9Gtg69axcaoYBt+NwEN7N/L0idvsr2TtpPrnCHilcOn32lfUPDG82mx/dat366sR4XW9ttUz9k1c/LV5fLylb4DGX0x/OjeuwMh0DoKF9yg/EjhrpHu4MtlgYKFIvTslJo0oTXcGTI5f2ihVdFEBEGGhOJB3latqWrprrBwa3Ez0kDl5lR8jd5oZv0CAd21RsO99ruyet55e8Wy+/9NKK/77g7/78HinlpmmaH9Fan+ldfvVT8Po1VlpL2VVq60IM6TDTzIkOGe44xBEXYOuEbViCeSyRcerhXtBlu26blewxnTcPY44yQLRBgca52KYz6BMTDL1sztM7jU00MiWjxOEP8S5WICK7EtrJgcvg0ULXOZrnmxitdQ+it/3B8LlvfPv37j+E/33r6xvnR8POF8JOozh6e004FzehdluzQbFM0VRxzAUSRJIhwX6GlOdySgJhocH5fhqgb9kqIgAcQgiYAXE2Yv1gQJRCYMjJlEI5yh/GIzo05oNMdUSRTSovPTaMhHvqcBpMUmIWUMkMItRhZ9f1fvrEkz8/9y/hf12heZxz/KTS+nO3b63cG/VvOvLyBoOmr8enLOoveiT3MQfxUkC6JigClDAF1NAKUuFgGSg2c4bUjINODbZPJF3nd9H7RUdFQUgaloVjmYcDs05M1YWBClFUGZs8kqpqxQGDE0oBkHOiewM/VFl87X3B/7Zms/mYUvjZKPIe8lu7VSn2S8mVthGzgCIJCH2jD3yoSBpr4tQYhAQwvydJDYnuGEwxhcxWSPYYp9IXMCdivWMbmACiiRrUkLKyleq+JVBMC6ofFbpUNQEVAEpJGzsuuAMVfWD4e7XbbdtPknsp4oME8R4AOg2g61HgV73RIGdorr1GK+/vbrPEyuxiMyJwgsvkUo+jDgxdtzANU8PeylT+42PS24iQFBixcijkyInh/kqaBcpwWiM4eNAE7gjl5OuqUDsWT0zO7P7b8H/WjRs3
Koh4qFwuZ1mWPYAIJwCwCAA5JKREEPJKqRnKmUcQbSCEESAeAqSISAmBKiKuEIAuALUQ9BglBBExopSuUkpfnp2dvfkX6a5m0ZqSUXAAAAAASUVORK5CYII="/></a></li>
+ </ul>
+
+ <p id="legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2013
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; Apache Qpid, Qpid, Qpid Proton,
+ Proton, Apache, the Apache feather logo, and the Apache Qpid
+ project logo are trademarks of The Apache Software
+ Foundation; All other marks mentioned may be trademarks or
+ registered trademarks of their respective owners
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Added: qpid/site/docs/releases/qpid-dispatch-0.1/release-0.1.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-0.1/release-0.1.html?rev=1559227&view=auto
==============================================================================
--- qpid/site/docs/releases/qpid-dispatch-0.1/release-0.1.html (added)
+++ qpid/site/docs/releases/qpid-dispatch-0.1/release-0.1.html Fri Jan 17 19:11:01 2014
@@ -0,0 +1,393 @@
+<!DOCTYPE html>
+<!--
+ -
+ - Licensed to the Apache Software Foundation (ASF) under one
+ - or more contributor license agreements. See the NOTICE file
+ - distributed with this work for additional information
+ - regarding copyright ownership. The ASF licenses this file
+ - to you under the Apache License, Version 2.0 (the
+ - "License"); you may not use this file except in compliance
+ - with the License. You may obtain a copy of the License at
+ -
+ - http://www.apache.org/licenses/LICENSE-2.0
+ -
+ - Unless required by applicable law or agreed to in writing,
+ - software distributed under the License is distributed on an
+ - "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ - KIND, either express or implied. See the License for the
+ - specific language governing permissions and limitations
+ - under the License.
+ -
+-->
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+ <head>
+ <title>Qpid Dispatch Release 0.1 - Apache Qpid™</title>
+ <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
+ <link rel="stylesheet" href="http://qpid.apache.org/site.css" type="text/css"/>
+ <link rel="stylesheet" href="http://qpid.apache.org/pygments.css" type="text/css"/>
+ <!--[if lte IE 8]>
+ <link rel="stylesheet" href="http://qpid.apache.org/ie.css" type="text/css"/>
+ <![endif]-->
+ <script type="text/javascript" src="http://qpid.apache.org/site.js"></script>
+ </head>
+ <body>
+ <div id="content">
+ <div id="top">
+ <a id="search-link" href="http://qpid.apache.org/search.html"><img width="22" height="16" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABUAAAAQCAYAAAD52jQlAAABmklEQVQ4y2P4//8/A7UxpkBoAxtPaIMTb2hdKW9I/WLe0Pp2nrC6YO7IKnGyDOUObTAAGnIRiP9j4oZPQJxGkqF8YXWRQE2/oAY84Q1rmMETUpfOF9LQBBQ7jGTBaqIM5YyolgUq/gjWBDRMxK+MF10hX0hdNFwNAReDCaCidVBXbManGGowJCgCK4VxGgoEjDAX8IfWKBLyGlDdSajBfjgN5Q2tUYe68jExkQBMEd1g9SH1rTgN5Q+tc4UaepwYQ/lC6/Khhi7GaShPYIMY1NDPDA0NTARdGtYwD2JoXTGBiKp/DFIIdIU3PgOFohv4gOqegtQCM4QjXkOBOagOlj75QhuE8ETSfKT0+pontK5aMLScH6uhDGlprEDDzkENfsAdUueMrIgrokEKKLcRKg/KIKeRDP8IzsrAYMTMUcE1qgiDwfgtEO8H4tvIBgDVRIGzdFiDC9CCfUjZ+BtvSIMPRt4HuzisoQGo6CVa3v8O1LQJlPMwg6TWEpRpoOGcjbWUgmFw1g2r8+UOr9VncGhgIZjfQ0OZYWwAIBYjaUYze6wAAAAASUVORK5CYII="/></a>
+
+ <ul id="global-navigation">
+ <li><a id="logotype" href="http://qpid.apache.org/index.html">Apache Qpid<sup>™</sup></a></li>
+ <li><a href="http://qpid.apache.org/download.html">Download</a></li>
+ <li><a href="http://qpid.apache.org/documentation.html">Documentation</a></li>
+ <li><a href="http://qpid.apache.org/discussion.html">Discussion</a></li>
+ <li><a href="http://qpid.apache.org/issues.html">Issues</a></li>
+ <li><a href="http://qpid.apache.org/source-code.html">Source Code</a></li>
+ <li><a href="http://qpid.apache.org/resources.html">More Resources</a></li>
+ </ul>
+ </div>
+ <div id="middle">
+ <ul id="path-navigation"><li><a href="http://qpid.apache.org/releases/index.html">Releases</a></li><li>Qpid Dispatch Release 0.1</li></ul>
+ <h1 id="qpid-dispatch-release-01">Qpid Dispatch Release 0.1</h1>
+
+<h2 id="system-requirements-and-dependencies">System Requirements and Dependencies</h2>
+
+<ul>
+<li>Qpid Dispatch will only build and run on Posix-based operating systems (Linux, et. al.)</li>
+<li>Qpid Proton version 0.6 must be installed (including the Python bindings) to build Qpid Dispatch</li>
+</ul>
+
+<h2 id="documented-capabilities-available-in-version-01">Documented capabilities available in version 0.1</h2>
+
+<p>Some of the capabilities listed in these pages for Dispatch are for future releases and are supplied for the purpose of illustrating the potential of a message router. This section outlines the actual capabilities of version 0.1:</p>
+
+<ul>
+<li>Route computation uses a fixed constant cost for inter-router links. Therefore, cost is only determined by the number of hops from source to destination.</li>
+<li>Addressing semantics are constrained to multicast. If there are multiple consumers for a particular address, each consumer will receive a copy of every message produced to that address.</li>
+<li>Link-Routing is not supported in 0.1. All routing is message-based.</li>
+<li>Broker integration is not yet implemented.</li>
+</ul>
+
+<h2 id="building-testing-and-installing">Building, Testing, and Installing</h2>
+
+<p>Download and extract the source tar file: <a href="http://www.apache.org/dyn/closer.cgi/qpid/dispatch/0.1/qpid-dispatch-0.1.tar.gz">qpid-dispatch-0.1.tar.gz</a> [<a href="http://www.apache.org/dist/qpid/dispatch/0.1/qpid-dispatch-0.1.tar.gz.asc">PGP</a>]</p>
+
+<pre><code>$ tar -xzf qpid-dispatch-0.1.tar.gz
+</code></pre>
+
+<p>Source the build configuration:</p>
+
+<pre><code>$ cd qpid-dispatch-0.1
+$ source config.sh
+</code></pre>
+
+<p>Build and test the package. This will create two directories: 'build' and 'install'. Dispatch will be built in the 'build' directory
+and installed in the 'install' directory. The regression and system test suites will then be run against the installed bits.</p>
+
+<pre><code>$ bin/test.sh
+</code></pre>
+
+<p>If you wish to change the build configuration, go into the build directory, use cmake to configure your build then rebuild and/or reinstall from there:</p>
+
+<pre><code>$ cd build
+$ cmake ..
+$ make
+$ make install
+</code></pre>
+
+<h2 id="configuration">Configuration</h2>
+
+<p>The default configuration file is installed in
+<em>install-prefix</em>/etc/qpid/qdrouterd.conf. This configuration file will cause the router
+to run in standalone mode, listening on the standard AMQP port (5672). Dispatch Router
+looks for the configuration file in the installed location by default. If you wish
+to use a different path, the "-c" command line option will instruct Dispatch Router as to
+which configuration to load.</p>
+
+<p>To run the router, invoke the executable:</p>
+
+<pre><code>$ qdrouterd
+</code></pre>
+
+<h2 id="client-compatibility">Client Compatibility</h2>
+
+<p>Dispatch Router should, in theory, work with any client that is compatible with AMQP 1.0.
+The following clients have been tested:</p>
+
+<table>
+<tbody>
+<tr><td><em>Client</em></td><td><em>Notes</em></td></tr>
+<tr><td>qpid::messaging</td><td>The Qpid messaging clients work with Dispatch Router as long as they are configured to use the 1.0 version of the protocol. To enable AMQP 1.0 in the C++ client, use the {protocol:amqp1.0} connection option.</td></tr>
+<tr><td>Proton Messenger</td><td>Messenger works with Dispatch Router.</td></tr>
+</tbody>
+</table>
+
+<h2 id="tools">Tools</h2>
+
+<p>Installed with the Dispatch Router kit is a command line tool called <em>qdstat</em>. This tool
+can be used to view manageable data inside Dispatch Router. The following options are
+useful for seeing that the router is doing:</p>
+
+<table>
+<tbody>
+<tr><td><em>Option</em></td><td><em>Description</em></td></tr>
+<tr><td>-l</td><td>Print a list of AMQP links attached to the router. Links are unidirectional. Outgoing links are usually associated with a subscription address. The tool distinguishes between <em>endpoint</em> links and <em>router</em> links. Endpoint links are attached to clients using the router. Router links are attached to other routers in a network of routers.</td></tr>
+<tr><td>-a</td><td>Print a list of addresses known to the router.</td></tr>
+<tr><td>-n</td><td>Print a list of known routers in the network.</td></tr>
+<tr><td>-c</td><td>Print a list of connections to the router.</td></tr>
+</tbody>
+</table>
+
+<h2 id="features-and-examples">Features and Examples</h2>
+
+<h3 id="standalone-and-interior-modes">Standalone and Interior Modes</h3>
+
+<p>The router can operate stand-alone or as a node in a network of routers. The mode is
+configured in the <em>router</em> section of the configuration file. In stand-alone mode, the
+router does not attempt to collaborate with any other routers and only routes messages
+among directly connected endpoints.</p>
+
+<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look like the following:</p>
+
+<pre><code>$ qdstat -a
+Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ===============================================================================
+ local $management Y 0 0 1 0 0 1 0
+ local temp.AY81ga 1 0 0 0 0 0 0
+</code></pre>
+
+<p>Note that there are two known addresses. <em>$management</em> is the address of the router's embedded management agent. <em>temp.AY81ga</em> is the temporary reply-to address of the <em>qdstat</em> client making requests to the agent.</p>
+
+<p>If you change the mode to interior and restart the processs, the same command will yield two additional addresses which are used for inter-router communication:</p>
+
+<pre><code>$ qdstat -a
+Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ===============================================================================
+ local $management Y 0 0 1 0 0 1 0
+ local qdhello Y 0 0 0 0 0 0 3
+ local qdrouter Y 0 0 0 0 0 0 1
+ local temp.khOpGb 1 0 0 0 0 0 0
+</code></pre>
+
+<h3 id="mobile-subscribers">Mobile Subscribers</h3>
+
+<p>The term "mobile subscriber" simply refers to the fact that a client may connect to the
+router and subscribe to an address to receive messages sent to that address. No matter
+where in the network the subscriber attaches, the messages will be routed to the
+appropriate destination.</p>
+
+<p>To illustrate a subscription on a stand-alone router, you can use the examples that are
+provided with Qpid Proton. Using the <em>recv.py</em> example receiver:</p>
+
+<pre><code>$ recv.py amqp://0.0.0.0/my-address
+</code></pre>
+
+<p>This command creates a receiving link subscribed to the specified address. To verify the
+subscription:</p>
+
+<pre><code>$ qdstat -a
+Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ================================================================================
+ local $management Y 0 0 1 0 0 1 0
+ mobile my-address 1 0 0 0 0 0 0
+ local temp.fDt8_a 1 0 0 0 0 0 0
+</code></pre>
+
+<p>You can then, in a separate command window, run a sender to produce messages to that
+address:</p>
+
+<pre><code>$ send.py -a amqp://0.0.0.0/my-address
+</code></pre>
+
+<h3 id="dynamic-reply-to">Dynamic Reply-To</h3>
+
+<p>Dynamic reply-to can be used to obtain a reply-to address that routes back to a client's
+receiving link regardless of how many hops it has to take to get there. To illustrate
+this feature, see below a simple program (written in C++ against the qpid::messaging API)
+that queries the management agent of the attached router for a list of other known
+routers' management addresses.</p>
+
+<pre><code>#include <qpid/messaging/Address.h>
+#include <qpid/messaging/Connection.h>
+#include <qpid/messaging/Message.h>
+#include <qpid/messaging/Receiver.h>
+#include <qpid/messaging/Sender.h>
+#include <qpid/messaging/Session.h>
+
+using namespace qpid::messaging;
+using namespace qpid::types;
+
+using std::stringstream;
+using std::string;
+
+int main() {
+ const char* url = "amqp:tcp:127.0.0.1:5672";
+ std::string connectionOptions = "{protocol:amqp1.0}";
+
+ Connection connection(url, connectionOptions);
+ connection.open();
+ Session session = connection.createSession();
+ Sender sender = session.createSender("mgmt");
+
+ // create reply receiver and get the reply-to address
+ Receiver receiver = session.createReceiver("#");
+ Address responseAddress = receiver.getAddress();
+
+ Message request;
+ request.setReplyTo(responseAddress);
+ request.setProperty("x-amqp-to", "amqp:/_local/$management");
+ request.setProperty("operation", "DISCOVER-MGMT-NODES");
+ request.setProperty("type", "org.amqp.management");
+ request.setProperty("name, "self");
+
+ sender.send(request);
+ Message response = receiver.fetch();
+ Variant content(response.getContentObject());
+ std::cout << "Response: " << content << std::endl << std::endl;
+
+ connection.close();
+}
+</code></pre>
+
+<p>The equivalent program written in Python against the Proton Messenger API:</p>
+
+<pre><code>from proton import Messenger, Message
+
+def main():
+ host = "0.0.0.0:5672"
+
+ messenger = Messenger()
+ messenger.start()
+ messenger.route("amqp:/*", "amqp://%s/$1" % host)
+ reply_subscription = messenger.subscribe("amqp:/#")
+ reply_address = reply_subscription.address
+
+ request = Message()
+ response = Message()
+
+ request.address = "amqp:/_local/$management"
+ request.reply_to = reply_address
+ request.properties = {u'operation' : u'DISCOVER-MGMT-NODES',
+ u'type' : u'org.amqp.management',
+ u'name' : u'self'}
+
+ messenger.put(request)
+ messenger.send()
+ messenger.recv()
+ messenger.get(response)
+
+ print "Response: %r" % response.body
+
+ messenger.stop()
+
+main()
+</code></pre>
+
+<h2 id="known-issues-and-limitations">Known Issues and Limitations</h2>
+
+<p>This is an early test release. It is expected that users will find bugs and other
+various instabilities. The main goal of this release is to prove that the process can be
+run and that users can demonstrate basic functionality as described in this document.
+Nevertheless, the following are known issues with the 0.1 release:</p>
+
+<ul>
+<li>Subscriber addresses are not always cleaned up after a consumer disconnects. See
+<a href="https://issues.apache.org/jira/browse/QPID-4964">https://issues.apache.org/jira/browse/QPID-4964</a>.</li>
+<li>Dispatch Router does not currently use the target address of a client's sender link to
+route messages. It only looks at the "to" field in the message's headers. See
+<a href="https://issues.apache.org/jira/browse/QPID-5175">https://issues.apache.org/jira/browse/QPID-5175</a>.</li>
+<li>All subscription sources are treated as multicast addresses. There is currently no
+facility for provisioning different types of addresses. Multicast means that if there
+are multiple subscribers to the same address, they will all receive a copy of each
+message sent to that address.</li>
+<li>SSL connectors and listeners are supported but very lightly (and not recently) tested.</li>
+<li>SASL authentication is not currently integrated into any authentication framework. Use
+ANONYMOUS for testing.</li>
+</ul>
+
+<h2 id="issues-addressed-in-this-release">Issues Addressed in this Release</h2>
+
+<ul>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4612">QPID-4612</a> Dispatch - Change server and container pattern to be consistent with other objects</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4613">QPID-4613</a> Dispatch Message API Improvements</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4614">QPID-4614</a> CTEST for Dispatch</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4788">QPID-4788</a> Dispatch - Re-schedule of an "immediate" timer causes crash</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4816">QPID-4816</a> dispatch-router crashes when incomplete (but valid) url specified by client.</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4853">QPID-4853</a> Connectors are not closed when connections are closed cleanly</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4913">QPID-4913</a> Dispatch - Add a configuration file reader to configure the service</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4963">QPID-4963</a> Dispatch - Excessive latency in timers under light load</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4967">QPID-4967</a> Dispatch - Distributed routing protocol to compute paths across a network of routers</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4968">QPID-4968</a> Dispatch - Generalized framework for embedded Python modules</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4974">QPID-4974</a> Dispatch - Improve the API for parsing and composing AMQP-typed fields</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-4997">QPID-4997</a> Dispatch - Thread safety issues in the usage of Proton</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5001">QPID-5001</a> Dispatch - A web page on the site for the Dispatch Router component</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5045">QPID-5045</a> Dispatch - Refactor the router data structures to allow both message-based and link-based routing that supports full link protocol</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5064">QPID-5064</a> Dispatch - make-install doesn't install the Python artifacts</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5066">QPID-5066</a> Dispatch - move Python code into the qpid.dispatch package</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5068">QPID-5068</a> Dispatch - Internal feature to easily add and update Delivery Annotations</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5096">QPID-5096</a> Dispatch - Install the configuration file</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5097">QPID-5097</a> Dispatch - create a source tarball</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5173">QPID-5173</a> [dispatch] cmake ignores overrides to CMAKE<em>INCLUDE</em>PATH and CMAKE<em>LIBRARY</em>PATH</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5181">QPID-5181</a> Dispatch - Assign temporary source addresses for dynamic listener links</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5185">QPID-5185</a> Move the qpid-dispatch.conf file to /etc/qpid</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5186">QPID-5186</a> Installing Dispatch should also install the LICENSE, TODO and related files</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5189">QPID-5189</a> Add a config.sh file for Qpid Dispatch to set an environment for running the router</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5201">QPID-5201</a> Dispatch - Fix build errors in Release mode</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5212">QPID-5212</a> Dispatch - Add management access to data in the router module</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5213">QPID-5213</a> Dispatch - Add a CLI tool to display manageable data in Dispatch</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5216">QPID-5216</a> Dispatch - Stabilization in anticipation of an early release</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5217">QPID-5217</a> Dispatch - Cleanup of API inconsistencies and oddities</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5218">QPID-5218</a> [dispatch] Crash when outgoing window > 0 and multiple subscribed Messenger clients</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5220">QPID-5220</a> Dispatch - Define Modes of Operation for the router function</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5221">QPID-5221</a> Dispatch - Configured connections can be annotated as to their role</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5257">QPID-5257</a> Dispatch - Move the code from trunk/qpid/extras to dispatch</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5258">QPID-5258</a> Dispatch - Prepare for Release 0.1</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5267">QPID-5267</a> Examples aren't being installed</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5310">QPID-5310</a> copy the correlationID into management replies</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5313">QPID-5313</a> qpid-dxrouterd binary should install the /usr/sbin on *nix</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5319">QPID-5319</a> Add ability to get list of connections through server management agent</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5335">QPID-5335</a> Dispatch Python libraries need to install to a private directory.</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5338">QPID-5338</a> The Dispatch top-level Python package should be renamed</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5339">QPID-5339</a> Dispatch - Intermittent crashes during scripted six-node tests</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5343">QPID-5343</a> Dispatch does not properly handle the drain protocol on senders.</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5350">QPID-5350</a> Dispatch - Management queries that receive empty tables results in corrupt response</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5351">QPID-5351</a> Settle on one prefix for Dispatch names</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5352">QPID-5352</a> Installation of python code ignores prefix</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5365">QPID-5365</a> Clean up file locations in Dispatch</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5367">QPID-5367</a> Dispatch - Add man pages and stubs for other documentation</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5380">QPID-5380</a> Dispatch - Simplify use of non-system instances</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5381">QPID-5381</a> Dispatch - Use dynamic source address for the reply-to in qdstat tool</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5392">QPID-5392</a> Dispatch - Remove ChangeLog; use jira and our website release pages instead</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5393">QPID-5393</a> Dispatch - Allow qdstat to query any router in the network from a connection</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5397">QPID-5397</a> Dispatch - Crash occurs when linked deliveries are concurrently settled</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5403">QPID-5403</a> Dispatch - The router-specific annotations have reserved keys</li>
+<li><a href="https://issues.apache.org/jira/browse/QPID-5448">QPID-5448</a> qdstat does not have the correct Python path for the internal libraries</li>
+</ul>
+
+ </div>
+ <div id="bottom">
+ <ul id="apache-navigation">
+ <li><a href="http://www.apache.org/">Apache</a></li>
+ <li><a href="http://www.apache.org/licenses/">License</a></li>
+ <li><a href="http://www.apache.org/foundation/sponsorship.html">Sponsorship</a></li>
+ <li><a href="http://www.apache.org/foundation/thanks.html">Thanks!</a></li>
+ <li><a href="http://www.apache.org/security/">Security</a></li>
+ <li><a href="http://www.apache.org/"><img id="apache-feather" width="48" height="14" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAC4AAAAOCAYAAABQFS4BAAAFnElEQVRIx83S22ukdx3H8e/v8Pyew5xnsrMJSZNsmm4PW91uL5ZWhIK9EA/Fq8Uiite9EuzVFhbxoqvd7kWLVEWEuioqpQgVtmpFssZtabpR9xCb7uQwmexMspPM5JmZ5/w8v9/v64UtiCi2StX3X/CCz4fMz8w8vN5qLSGihnf7ypkzdw333Eeaq43f/G7xtRb8H0bOnz//+He/9cLjCHpZEfL9ZrN5+9wLL55GUJ/f2W7B3M+WnzZRfqmAukA0jgpVfu1NHF1dGHZ+abbnswVckP8T+Orq6tEwjJ5/9plvlv5wZflO1PriY6dOYcwKX6xWyli/uLUaRf2jdwRUTBGl+kL6PA5HlVGQ2zNVK7T0WlJhr1wW6hcvLizE/zU4IsLS0lKxVjv09dXVP3/5RxcuHNy4dn18/r77LCIKOBFN+XWds4uQcuEOCKOZOr6b8O6E0OV+AGUtVd+I99JS4ks3XWncgctqlv36qe+9dvVDh79Xo9E4ufzH61/b6e5/YnHxEvY7bYPGNs5Wj+s8q4GdY7TkR8gxFGNdATiZKifwyHTXBZnPqZR4EScq9aNQxfPkem8YvVPhxhu/Pch+9YM/LQw+NPgTp0/PVuzydxTwh6M4sk9gLrj51nZxhwWqPdwgeXFYVcQkpdqgRlbmDhI1z3sqsyjPp4GquSMSCIrTUUATJlJSSKMeCePJ7TTr5OTQrBsH7JAY9kDK3n504WK7/ebi2tr+fww/e/bcZ6rj489YljNj2zYUnv6x50VpXRoFFGmFL9QTKR2qtocbdDAI+HhlBkp0QumUkgckI/0q6OPuEHrlHFaTEea
TGHUA3MwzXXB9Gtg69axcaoYBt+NwEN7N/L0idvsr2TtpPrnCHilcOn32lfUPDG82mx/dat366sR4XW9ttUz9k1c/LV5fLylb4DGX0x/OjeuwMh0DoKF9yg/EjhrpHu4MtlgYKFIvTslJo0oTXcGTI5f2ihVdFEBEGGhOJB3latqWrprrBwa3Ez0kDl5lR8jd5oZv0CAd21RsO99ruyet55e8Wy+/9NKK/77g7/78HinlpmmaH9Fan+ldfvVT8Po1VlpL2VVq60IM6TDTzIkOGe44xBEXYOuEbViCeSyRcerhXtBlu26blewxnTcPY44yQLRBgca52KYz6BMTDL1sztM7jU00MiWjxOEP8S5WICK7EtrJgcvg0ULXOZrnmxitdQ+it/3B8LlvfPv37j+E/33r6xvnR8POF8JOozh6e004FzehdluzQbFM0VRxzAUSRJIhwX6GlOdySgJhocH5fhqgb9kqIgAcQgiYAXE2Yv1gQJRCYMjJlEI5yh/GIzo05oNMdUSRTSovPTaMhHvqcBpMUmIWUMkMItRhZ9f1fvrEkz8/9y/hf12heZxz/KTS+nO3b63cG/VvOvLyBoOmr8enLOoveiT3MQfxUkC6JigClDAF1NAKUuFgGSg2c4bUjINODbZPJF3nd9H7RUdFQUgaloVjmYcDs05M1YWBClFUGZs8kqpqxQGDE0oBkHOiewM/VFl87X3B/7Zms/mYUvjZKPIe8lu7VSn2S8mVthGzgCIJCH2jD3yoSBpr4tQYhAQwvydJDYnuGEwxhcxWSPYYp9IXMCdivWMbmACiiRrUkLKyleq+JVBMC6ofFbpUNQEVAEpJGzsuuAMVfWD4e7XbbdtPknsp4oME8R4AOg2g61HgV73RIGdorr1GK+/vbrPEyuxiMyJwgsvkUo+jDgxdtzANU8PeylT+42PS24iQFBixcijkyInh/kqaBcpwWiM4eNAE7gjl5OuqUDsWT0zO7P7b8H/WjRs3
Koh4qFwuZ1mWPYAIJwCwCAA5JKREEPJKqRnKmUcQbSCEESAeAqSISAmBKiKuEIAuALUQ9BglBBExopSuUkpfnp2dvfkX6a5m0ZqSUXAAAAAASUVORK5CYII="/></a></li>
+ </ul>
+
+ <p id="legal">
+ Apache Qpid, Messaging built on AMQP; Copyright © 2013
+ The Apache Software Foundation; Licensed under
+ the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+ License, Version 2.0</a>; Apache Qpid, Qpid, Qpid Proton,
+ Proton, Apache, the Apache feather logo, and the Apache Qpid
+ project logo are trademarks of The Apache Software
+ Foundation; All other marks mentioned may be trademarks or
+ registered trademarks of their respective owners
+ </p>
+ </div>
+ </div>
+ </body>
+</html>
Modified: qpid/site/docs/site.conf
URL: http://svn.apache.org/viewvc/qpid/site/docs/site.conf?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/docs/site.conf (original)
+++ qpid/site/docs/site.conf Fri Jan 17 19:11:01 2014
@@ -7,3 +7,7 @@ current-proton-release = 0.6
current-proton-release-url = %(site-url)s/releases/qpid-proton-%(current-proton-release)s
current-proton-release-link = <a href="%(current-proton-release-url)s/index.html">Qpid Proton %(current-proton-release)s</a>
current-proton-release-tag = http://svn.apache.org/repos/asf/qpid/proton/tags/%(current-proton-release)s
+current-dispatch-release = 0.1
+current-dispatch-release-url = %(site-url)s/releases/qpid-dispatch-%(current-dispatch-release)s
+current-dispatch-release-link = <a href="%(current-dispatch-release-url)s/index.html">Qpid Dispatch %(current-dispatch-release)s</a>
+current-dispatch-release-tag = http://svn.apache.org/repos/asf/qpid/dispatch/tags/%(current-dispatch-release)s
Modified: qpid/site/input/components/dispatch-router/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch-router/index.md?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/input/components/dispatch-router/index.md (original)
+++ qpid/site/input/components/dispatch-router/index.md Fri Jan 17 19:11:01 2014
@@ -26,11 +26,9 @@ and brokers.
|| *Platforms* || Linux ||
|| *AMQP versions* || 1.0 ||
- || *Download* || <http://people.apache.org/~tross/qpid-dispatch-0.1rc5/> ||
+ || *Download* || [qpid-dispatch-@current-dispatch-release@.tar.gz](http://www.apache.org/dyn/closer.cgi/qpid/dispatch/@current-dispatch-release@/qpid-dispatch-@current-dispatch-release@.tar.gz) \[[PGP](http://www.apache.org/dist/qpid/dispatch/@current-dispatch-release@/qpid-dispatch-@current-dispatch-release@.tar.gz.asc)] ||
|| *Source location* || <http://svn.apache.org/repos/asf/qpid/dispatch/trunk/> ||
-[What can you do with Qpid Dispatch 0.1?](release-0.1.html)
-
## Overview
The Dispatch router is an AMQP router that provides advanced interconnect for AMQP.
@@ -72,11 +70,12 @@ involving a broker at all.
</div>
-## Technical Details
+## Documentation
<div class="two-column" markdown="1">
- - [Usage of AMQP](amqp-mapping.html)
+ - [Initial Release Overview](@current-dispatch-release-url@/release-0.1.html)
+ - [Usage of AMQP](@current-dispatch-release-url@/amqp-mapping.html)
</div>
Modified: qpid/site/input/index.html
URL: http://svn.apache.org/viewvc/qpid/site/input/index.html?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/input/index.html (original)
+++ qpid/site/input/index.html Fri Jan 17 19:11:01 2014
@@ -79,6 +79,7 @@
<ul>
<li><a href="@site-url@/components/java-broker/index.html">Java broker</a> - A pure-Java AMQP message broker</li>
<li><a href="@site-url@/components/cpp-broker/index.html">C++ broker</a> - A native-code AMQP message broker</li>
+ <li><a href="@site-url@/components/dispatch-router/index.html">Dispatch Router</a> - A lightweight AMQP message router</li>
<li>More about <a href="@site-url@/components/index.html#servers-and-tools">Qpid servers and tools</a></li>
</ul>
</div>
Modified: qpid/site/input/releases/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/index.md?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/input/releases/index.md (original)
+++ qpid/site/input/releases/index.md Fri Jan 17 19:11:01 2014
@@ -29,6 +29,7 @@ and the
- [Qpid 0.24](qpid-0.24/index.html), September 2013
- [Qpid Proton 0.6](qpid-proton-0.6/index.html), January 2014
+ - [Qpid Dispatch 0.1](qpid-dispatch-0.1/index.html), January 2014
## Past releases
Added: qpid/site/input/releases/qpid-dispatch-0.1/amqp-mapping.md
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-0.1/amqp-mapping.md?rev=1559227&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-0.1/amqp-mapping.md (added)
+++ qpid/site/input/releases/qpid-dispatch-0.1/amqp-mapping.md Fri Jan 17 19:11:01 2014
@@ -0,0 +1,101 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+# Dispatch AMQP Mapping
+
+Dispatch Router is an AMQP router and as such, it provides extensions,
+codepoints, and semantics for routing over AMQP. This page documents
+the details of Dispatch Router's use of AMQP.
+
+
+## Delivery Annotations
+
+The following Delivery Annotation fields are defined by Dispatch Router:
+
+ || *Field* || *Type* || *Description* ||
+ || <span style="white-space: nowrap;">x-opt-qd.ingress</span> || string || The identity of the ingress router for a message-routed message. The ingress router is the first router encountered by a transiting message. The router will, if this field is present, leave it unaltered. If the field is not present, the router shall insert the field with its own identity. ||
+ || <span style="white-space: nowrap;">x-opt-qd.trace</span> || list of string || The list of routers through which this message-routed message has transited. If this field is not present, the router shall do nothing. If the field is present, the router shall append its own identity to the end of the list. ||
+ || x-opt-qd.to || string || To-Override for message-routed messages. If this field is present, the address in this field shall be used for routing in lieu of the *to* field in the message properties. A router may append, remove, or modify this annotation field depending on the policy in place for routing the message. ||
+
+
+## Source/Target Capabilities
+
+The following Capability values are used in Sources and Targets.
+
+ || *Capability* || *Description* ||
+ || qd.router || This capability is added to sources and targets that are used for inter-router message exchange. ||
+
+
+## Addresses and Address Formats
+
+The following AMQP addresses and address patterns are used within Dispatch Router.
+
+### Address Patterns
+
+ || *Pattern* || *Description* ||
+ || /_local/<addr> || An address that references a locally attached endpoint. Messages using this address pattern shall not be routed over more than one link. ||
+ || <span style="white-space: nowrap;">/_topo/<area>/<router>/<addr></span> || An address that references an endpoint attached to a specific router node in the network topology. Messages with addresses that follow this pattern shall be routed along the shortest path to the specified router. Note that addresses of this form are a-priori routable in that the address itself contains enough information to route the message to its destination. ||
+ || /<addr> || A mobile address. An address of this format represents an endpoint or a set of distinct endpoints that are attached to the network in arbitrary locations. It is the responsibility of the router network to determine which router nodes are valid destinations for mobile addresses. ||
+
+### Supported Addresses
+
+ || *Address* || *Description* ||
+ || /_local/$management || The management agent on the attached router/container. This address would be used by an endpoint that is a management client/console/tool wishing to access management data from the attached container. ||
+ || <span style="white-space: nowrap;">/_topo/0/Router.E/agent</span> || The management agent at Router.E in area 0. This address would be used by a management client wishing to access management data from a specific container that is reachable within the network. ||
+ || /_local/qdhello || The router entity in each of the connected routers. This address is used to communicate with neighbor routers and is exclusively for the HELLO discovery protocol. ||
+ || /_local/qdrouter || The router entity in each of the connected routers. This address is used by a router to communicate with other routers in the network. ||
+ || <span style="white-space: nowrap;">/_topo/0/Router.E/qdxrouter</span> || The router entity at the specifically indicated router. This address form is used by a router to communicate with a specific router that may or may not be a neighbor. ||
+
+## Implementation of the AMQP Management Specification
+
+Qpid Dispatch is manageable remotely via AMQP. It is compliant to a limited degree with the emerging AMQP Management specification. This section provides the details of what is supported and what is not and what is planned and what is not.
+
+Non-compliance occurs for one of the following reasons:
+
+ - Implementation of an optional feature is not planned
+ - Implementation is not complete as of the current time
+ - The specified operation is considered suboptimal or unimplementable. In all of these cases, an issue is pending with the AMQP Technical Committee.
+
+### Compliance Matrix
+
+ || *Operation/Feature* || *Requirement* || *Supported* || *Remarks* ||
+ || CREATE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || READ || Should || No || Not yet implemented ||
+ || UPDATE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || DELETE || Should || No || There are currently no Manageable Entities for which this is appropriate ||
+ || READALL || Should || No || A non-standard version of this operation is supported that retrieves data from all entities of a type. There is an outstanding issue raised with the AMQP Technical Committee to address this requirement. ||
+ || DISCOVER-NAMES || Should || No || Not yet implemented ||
+ || DISCOVER-TYPES || Should || Yes || There are no types that implement base types ||
+ || DISCOVER-OPERATIONS || Should || Yes || ||
+ || DISCOVER-MGMT-NODES || Should || Yes || This operation yields the addresses of all of the router nodes in the known network ||
+ || REGISTER || May || Not Planned || The router has a specific way to discover peers that does not involve this operation ||
+ || DEREGISTER || May || Not Planned || The router has a specific way to discover peers that does not involve this operation ||
+
+### Manageable Entities
+
+ || *Type Name* || *Description* ||
+ || org.apache.qpid.dispatch.allocator || Per-type memory allocation statistics ||
+ || org.apache.qpid.dispatch.connection || Connections to the router's container ||
+ || org.apache.qpid.dispatch.container || General state and statistics for the AMQP container ||
+ || org.apache.qpid.dispatch.container.node_type || Description of registered node types ||
+ || org.apache.qpid.dispatch.container.node || Description of registered nodes in the container ||
+ || org.apache.qpid.dispatch.router || General state and statistics for the router node ||
+ || org.apache.qpid.dispatch.router.link || Per-link state and statistics for links attached to the router node ||
+ || org.apache.qpid.dispatch.router.node || Per-node state and statistics for remote router nodes in the known network ||
+ || org.apache.qpid.dispatch.router.address || Per-address state and statistics for addresses known to this router ||
Added: qpid/site/input/releases/qpid-dispatch-0.1/release-0.1.md
URL: http://svn.apache.org/viewvc/qpid/site/input/releases/qpid-dispatch-0.1/release-0.1.md?rev=1559227&view=auto
==============================================================================
--- qpid/site/input/releases/qpid-dispatch-0.1/release-0.1.md (added)
+++ qpid/site/input/releases/qpid-dispatch-0.1/release-0.1.md Fri Jan 17 19:11:01 2014
@@ -0,0 +1,311 @@
+;;
+;; Licensed to the Apache Software Foundation (ASF) under one
+;; or more contributor license agreements. See the NOTICE file
+;; distributed with this work for additional information
+;; regarding copyright ownership. The ASF licenses this file
+;; to you under the Apache License, Version 2.0 (the
+;; "License"); you may not use this file except in compliance
+;; with the License. You may obtain a copy of the License at
+;;
+;; http://www.apache.org/licenses/LICENSE-2.0
+;;
+;; Unless required by applicable law or agreed to in writing,
+;; software distributed under the License is distributed on an
+;; "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+;; KIND, either express or implied. See the License for the
+;; specific language governing permissions and limitations
+;; under the License.
+;;
+
+# Qpid Dispatch Release 0.1
+
+## System Requirements and Dependencies
+
+ - Qpid Dispatch will only build and run on Posix-based operating systems (Linux, et. al.)
+ - Qpid Proton version 0.6 must be installed (including the Python bindings) to build Qpid Dispatch
+
+## Documented capabilities available in version 0.1
+
+Some of the capabilities listed in these pages for Dispatch are for future releases and are supplied for the purpose of illustrating the potential of a message router. This section outlines the actual capabilities of version 0.1:
+
+ - Route computation uses a fixed constant cost for inter-router links. Therefore, cost is only determined by the number of hops from source to destination.
+ - Addressing semantics are constrained to multicast. If there are multiple consumers for a particular address, each consumer will receive a copy of every message produced to that address.
+ - Link-Routing is not supported in 0.1. All routing is message-based.
+ - Broker integration is not yet implemented.
+
+## Building, Testing, and Installing
+
+Download and extract the source tar file: [qpid-dispatch-@current-dispatch-release@.tar.gz](http://www.apache.org/dyn/closer.cgi/qpid/dispatch/@current-dispatch-release@/qpid-dispatch-@current-dispatch-release@.tar.gz) \[[PGP](http://www.apache.org/dist/qpid/dispatch/@current-dispatch-release@/qpid-dispatch-@current-dispatch-release@.tar.gz.asc)]
+
+ $ tar -xzf qpid-dispatch-0.1.tar.gz
+
+Source the build configuration:
+
+ $ cd qpid-dispatch-0.1
+ $ source config.sh
+
+Build and test the package. This will create two directories: 'build' and 'install'. Dispatch will be built in the 'build' directory
+and installed in the 'install' directory. The regression and system test suites will then be run against the installed bits.
+
+ $ bin/test.sh
+
+If you wish to change the build configuration, go into the build directory, use cmake to configure your build then rebuild and/or reinstall from there:
+
+ $ cd build
+ $ cmake ..
+ $ make
+ $ make install
+
+## Configuration
+
+The default configuration file is installed in
+_install-prefix_/etc/qpid/qdrouterd.conf. This configuration file will cause the router
+to run in standalone mode, listening on the standard AMQP port (5672). Dispatch Router
+looks for the configuration file in the installed location by default. If you wish
+to use a different path, the "-c" command line option will instruct Dispatch Router as to
+which configuration to load.
+
+To run the router, invoke the executable:
+
+ $ qdrouterd
+
+## Client Compatibility
+
+Dispatch Router should, in theory, work with any client that is compatible with AMQP 1.0.
+The following clients have been tested:
+
+ || *Client* || *Notes* ||
+ || qpid::messaging || The Qpid messaging clients work with Dispatch Router as long as they are configured to use the 1.0 version of the protocol. To enable AMQP 1.0 in the C++ client, use the {protocol:amqp1.0} connection option. ||
+ || Proton Messenger || Messenger works with Dispatch Router. ||
+
+## Tools
+
+Installed with the Dispatch Router kit is a command line tool called *qdstat*. This tool
+can be used to view manageable data inside Dispatch Router. The following options are
+useful for seeing that the router is doing:
+
+ || *Option* || *Description* ||
+ || -l || Print a list of AMQP links attached to the router. Links are unidirectional. Outgoing links are usually associated with a subscription address. The tool distinguishes between _endpoint_ links and _router_ links. Endpoint links are attached to clients using the router. Router links are attached to other routers in a network of routers. ||
+ || -a || Print a list of addresses known to the router. ||
+ || -n || Print a list of known routers in the network. ||
+ || -c || Print a list of connections to the router. ||
+
+## Features and Examples
+
+### Standalone and Interior Modes
+
+The router can operate stand-alone or as a node in a network of routers. The mode is
+configured in the _router_ section of the configuration file. In stand-alone mode, the
+router does not attempt to collaborate with any other routers and only routes messages
+among directly connected endpoints.
+
+If your router is running in stand-alone mode, _qdstat -a_ will look like the following:
+
+ $ qdstat -a
+ Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ===============================================================================
+ local $management Y 0 0 1 0 0 1 0
+ local temp.AY81ga 1 0 0 0 0 0 0
+
+Note that there are two known addresses. _$management_ is the address of the router's embedded management agent. _temp.AY81ga_ is the temporary reply-to address of the _qdstat_ client making requests to the agent.
+
+If you change the mode to interior and restart the processs, the same command will yield two additional addresses which are used for inter-router communication:
+
+ $ qdstat -a
+ Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ===============================================================================
+ local $management Y 0 0 1 0 0 1 0
+ local qdhello Y 0 0 0 0 0 0 3
+ local qdrouter Y 0 0 0 0 0 0 1
+ local temp.khOpGb 1 0 0 0 0 0 0
+
+
+### Mobile Subscribers
+
+The term "mobile subscriber" simply refers to the fact that a client may connect to the
+router and subscribe to an address to receive messages sent to that address. No matter
+where in the network the subscriber attaches, the messages will be routed to the
+appropriate destination.
+
+To illustrate a subscription on a stand-alone router, you can use the examples that are
+provided with Qpid Proton. Using the _recv.py_ example receiver:
+
+ $ recv.py amqp://0.0.0.0/my-address
+
+This command creates a receiving link subscribed to the specified address. To verify the
+subscription:
+
+ $ qdstat -a
+ Router Addresses
+ class address in-proc local remote in out thru to-proc from-proc
+ ================================================================================
+ local $management Y 0 0 1 0 0 1 0
+ mobile my-address 1 0 0 0 0 0 0
+ local temp.fDt8_a 1 0 0 0 0 0 0
+
+You can then, in a separate command window, run a sender to produce messages to that
+address:
+
+ $ send.py -a amqp://0.0.0.0/my-address
+
+### Dynamic Reply-To
+
+Dynamic reply-to can be used to obtain a reply-to address that routes back to a client's
+receiving link regardless of how many hops it has to take to get there. To illustrate
+this feature, see below a simple program (written in C++ against the qpid::messaging API)
+that queries the management agent of the attached router for a list of other known
+routers' management addresses.
+
+ #include <qpid/messaging/Address.h>
+ #include <qpid/messaging/Connection.h>
+ #include <qpid/messaging/Message.h>
+ #include <qpid/messaging/Receiver.h>
+ #include <qpid/messaging/Sender.h>
+ #include <qpid/messaging/Session.h>
+
+ using namespace qpid::messaging;
+ using namespace qpid::types;
+
+ using std::stringstream;
+ using std::string;
+
+ int main() {
+ const char* url = "amqp:tcp:127.0.0.1:5672";
+ std::string connectionOptions = "{protocol:amqp1.0}";
+
+ Connection connection(url, connectionOptions);
+ connection.open();
+ Session session = connection.createSession();
+ Sender sender = session.createSender("mgmt");
+
+ // create reply receiver and get the reply-to address
+ Receiver receiver = session.createReceiver("#");
+ Address responseAddress = receiver.getAddress();
+
+ Message request;
+ request.setReplyTo(responseAddress);
+ request.setProperty("x-amqp-to", "amqp:/_local/$management");
+ request.setProperty("operation", "DISCOVER-MGMT-NODES");
+ request.setProperty("type", "org.amqp.management");
+ request.setProperty("name, "self");
+
+ sender.send(request);
+ Message response = receiver.fetch();
+ Variant content(response.getContentObject());
+ std::cout << "Response: " << content << std::endl << std::endl;
+
+ connection.close();
+ }
+
+The equivalent program written in Python against the Proton Messenger API:
+
+ from proton import Messenger, Message
+
+ def main():
+ host = "0.0.0.0:5672"
+
+ messenger = Messenger()
+ messenger.start()
+ messenger.route("amqp:/*", "amqp://%s/$1" % host)
+ reply_subscription = messenger.subscribe("amqp:/#")
+ reply_address = reply_subscription.address
+
+ request = Message()
+ response = Message()
+
+ request.address = "amqp:/_local/$management"
+ request.reply_to = reply_address
+ request.properties = {u'operation' : u'DISCOVER-MGMT-NODES',
+ u'type' : u'org.amqp.management',
+ u'name' : u'self'}
+
+ messenger.put(request)
+ messenger.send()
+ messenger.recv()
+ messenger.get(response)
+
+ print "Response: %r" % response.body
+
+ messenger.stop()
+
+ main()
+
+
+## Known Issues and Limitations
+
+This is an early test release. It is expected that users will find bugs and other
+various instabilities. The main goal of this release is to prove that the process can be
+run and that users can demonstrate basic functionality as described in this document.
+Nevertheless, the following are known issues with the 0.1 release:
+
+ - Subscriber addresses are not always cleaned up after a consumer disconnects. See
+ <https://issues.apache.org/jira/browse/QPID-4964>.
+ - Dispatch Router does not currently use the target address of a client's sender link to
+ route messages. It only looks at the "to" field in the message's headers. See
+ <https://issues.apache.org/jira/browse/QPID-5175>.
+ - All subscription sources are treated as multicast addresses. There is currently no
+ facility for provisioning different types of addresses. Multicast means that if there
+ are multiple subscribers to the same address, they will all receive a copy of each
+ message sent to that address.
+ - SSL connectors and listeners are supported but very lightly (and not recently) tested.
+ - SASL authentication is not currently integrated into any authentication framework. Use
+ ANONYMOUS for testing.
+
+## Issues Addressed in this Release
+
+ - [QPID-4612](https://issues.apache.org/jira/browse/QPID-4612) Dispatch - Change server and container pattern to be consistent with other objects
+ - [QPID-4613](https://issues.apache.org/jira/browse/QPID-4613) Dispatch Message API Improvements
+ - [QPID-4614](https://issues.apache.org/jira/browse/QPID-4614) CTEST for Dispatch
+ - [QPID-4788](https://issues.apache.org/jira/browse/QPID-4788) Dispatch - Re-schedule of an "immediate" timer causes crash
+ - [QPID-4816](https://issues.apache.org/jira/browse/QPID-4816) dispatch-router crashes when incomplete (but valid) url specified by client.
+ - [QPID-4853](https://issues.apache.org/jira/browse/QPID-4853) Connectors are not closed when connections are closed cleanly
+ - [QPID-4913](https://issues.apache.org/jira/browse/QPID-4913) Dispatch - Add a configuration file reader to configure the service
+ - [QPID-4963](https://issues.apache.org/jira/browse/QPID-4963) Dispatch - Excessive latency in timers under light load
+ - [QPID-4967](https://issues.apache.org/jira/browse/QPID-4967) Dispatch - Distributed routing protocol to compute paths across a network of routers
+ - [QPID-4968](https://issues.apache.org/jira/browse/QPID-4968) Dispatch - Generalized framework for embedded Python modules
+ - [QPID-4974](https://issues.apache.org/jira/browse/QPID-4974) Dispatch - Improve the API for parsing and composing AMQP-typed fields
+ - [QPID-4997](https://issues.apache.org/jira/browse/QPID-4997) Dispatch - Thread safety issues in the usage of Proton
+ - [QPID-5001](https://issues.apache.org/jira/browse/QPID-5001) Dispatch - A web page on the site for the Dispatch Router component
+ - [QPID-5045](https://issues.apache.org/jira/browse/QPID-5045) Dispatch - Refactor the router data structures to allow both message-based and link-based routing that supports full link protocol
+ - [QPID-5064](https://issues.apache.org/jira/browse/QPID-5064) Dispatch - make-install doesn't install the Python artifacts
+ - [QPID-5066](https://issues.apache.org/jira/browse/QPID-5066) Dispatch - move Python code into the qpid.dispatch package
+ - [QPID-5068](https://issues.apache.org/jira/browse/QPID-5068) Dispatch - Internal feature to easily add and update Delivery Annotations
+ - [QPID-5096](https://issues.apache.org/jira/browse/QPID-5096) Dispatch - Install the configuration file
+ - [QPID-5097](https://issues.apache.org/jira/browse/QPID-5097) Dispatch - create a source tarball
+ - [QPID-5173](https://issues.apache.org/jira/browse/QPID-5173) [dispatch] cmake ignores overrides to CMAKE_INCLUDE_PATH and CMAKE_LIBRARY_PATH
+ - [QPID-5181](https://issues.apache.org/jira/browse/QPID-5181) Dispatch - Assign temporary source addresses for dynamic listener links
+ - [QPID-5185](https://issues.apache.org/jira/browse/QPID-5185) Move the qpid-dispatch.conf file to /etc/qpid
+ - [QPID-5186](https://issues.apache.org/jira/browse/QPID-5186) Installing Dispatch should also install the LICENSE, TODO and related files
+ - [QPID-5189](https://issues.apache.org/jira/browse/QPID-5189) Add a config.sh file for Qpid Dispatch to set an environment for running the router
+ - [QPID-5201](https://issues.apache.org/jira/browse/QPID-5201) Dispatch - Fix build errors in Release mode
+ - [QPID-5212](https://issues.apache.org/jira/browse/QPID-5212) Dispatch - Add management access to data in the router module
+ - [QPID-5213](https://issues.apache.org/jira/browse/QPID-5213) Dispatch - Add a CLI tool to display manageable data in Dispatch
+ - [QPID-5216](https://issues.apache.org/jira/browse/QPID-5216) Dispatch - Stabilization in anticipation of an early release
+ - [QPID-5217](https://issues.apache.org/jira/browse/QPID-5217) Dispatch - Cleanup of API inconsistencies and oddities
+ - [QPID-5218](https://issues.apache.org/jira/browse/QPID-5218) [dispatch] Crash when outgoing window > 0 and multiple subscribed Messenger clients
+ - [QPID-5220](https://issues.apache.org/jira/browse/QPID-5220) Dispatch - Define Modes of Operation for the router function
+ - [QPID-5221](https://issues.apache.org/jira/browse/QPID-5221) Dispatch - Configured connections can be annotated as to their role
+ - [QPID-5257](https://issues.apache.org/jira/browse/QPID-5257) Dispatch - Move the code from trunk/qpid/extras to dispatch
+ - [QPID-5258](https://issues.apache.org/jira/browse/QPID-5258) Dispatch - Prepare for Release 0.1
+ - [QPID-5267](https://issues.apache.org/jira/browse/QPID-5267) Examples aren't being installed
+ - [QPID-5310](https://issues.apache.org/jira/browse/QPID-5310) copy the correlationID into management replies
+ - [QPID-5313](https://issues.apache.org/jira/browse/QPID-5313) qpid-dxrouterd binary should install the /usr/sbin on *nix
+ - [QPID-5319](https://issues.apache.org/jira/browse/QPID-5319) Add ability to get list of connections through server management agent
+ - [QPID-5335](https://issues.apache.org/jira/browse/QPID-5335) Dispatch Python libraries need to install to a private directory.
+ - [QPID-5338](https://issues.apache.org/jira/browse/QPID-5338) The Dispatch top-level Python package should be renamed
+ - [QPID-5339](https://issues.apache.org/jira/browse/QPID-5339) Dispatch - Intermittent crashes during scripted six-node tests
+ - [QPID-5343](https://issues.apache.org/jira/browse/QPID-5343) Dispatch does not properly handle the drain protocol on senders.
+ - [QPID-5350](https://issues.apache.org/jira/browse/QPID-5350) Dispatch - Management queries that receive empty tables results in corrupt response
+ - [QPID-5351](https://issues.apache.org/jira/browse/QPID-5351) Settle on one prefix for Dispatch names
+ - [QPID-5352](https://issues.apache.org/jira/browse/QPID-5352) Installation of python code ignores prefix
+ - [QPID-5365](https://issues.apache.org/jira/browse/QPID-5365) Clean up file locations in Dispatch
+ - [QPID-5367](https://issues.apache.org/jira/browse/QPID-5367) Dispatch - Add man pages and stubs for other documentation
+ - [QPID-5380](https://issues.apache.org/jira/browse/QPID-5380) Dispatch - Simplify use of non-system instances
+ - [QPID-5381](https://issues.apache.org/jira/browse/QPID-5381) Dispatch - Use dynamic source address for the reply-to in qdstat tool
+ - [QPID-5392](https://issues.apache.org/jira/browse/QPID-5392) Dispatch - Remove ChangeLog; use jira and our website release pages instead
+ - [QPID-5393](https://issues.apache.org/jira/browse/QPID-5393) Dispatch - Allow qdstat to query any router in the network from a connection
+ - [QPID-5397](https://issues.apache.org/jira/browse/QPID-5397) Dispatch - Crash occurs when linked deliveries are concurrently settled
+ - [QPID-5403](https://issues.apache.org/jira/browse/QPID-5403) Dispatch - The router-specific annotations have reserved keys
+ - [QPID-5448](https://issues.apache.org/jira/browse/QPID-5448) qdstat does not have the correct Python path for the internal libraries
Modified: qpid/site/input/site.conf
URL: http://svn.apache.org/viewvc/qpid/site/input/site.conf?rev=1559227&r1=1559226&r2=1559227&view=diff
==============================================================================
--- qpid/site/input/site.conf (original)
+++ qpid/site/input/site.conf Fri Jan 17 19:11:01 2014
@@ -7,3 +7,7 @@ current-proton-release = 0.6
current-proton-release-url = %(site-url)s/releases/qpid-proton-%(current-proton-release)s
current-proton-release-link = <a href="%(current-proton-release-url)s/index.html">Qpid Proton %(current-proton-release)s</a>
current-proton-release-tag = http://svn.apache.org/repos/asf/qpid/proton/tags/%(current-proton-release)s
+current-dispatch-release = 0.1
+current-dispatch-release-url = %(site-url)s/releases/qpid-dispatch-%(current-dispatch-release)s
+current-dispatch-release-link = <a href="%(current-dispatch-release-url)s/index.html">Qpid Dispatch %(current-dispatch-release)s</a>
+current-dispatch-release-tag = http://svn.apache.org/repos/asf/qpid/dispatch/tags/%(current-dispatch-release)s
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org