You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@qpid.apache.org by ac...@apache.org on 2016/06/30 19:47:50 UTC
[01/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Repository: qpid-site
Updated Branches:
refs/heads/asf-site 3e3e9ea18 -> 18828d3b5
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdstat.8.html
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdstat.8.html b/input/releases/qpid-dispatch-master/qdstat.8.html
deleted file mode 100644
index 529b962..0000000
--- a/input/releases/qpid-dispatch-master/qdstat.8.html
+++ /dev/null
@@ -1,1467 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdstat(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdstat(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
-<p>qdstat -
- show status and statistics for a running 'qdrouterd'
-</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdstat</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Shows status information about networks of Dispatch routers. It can display
-connections, network nodes and links, and router stats such as memory use.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>-g, --general
-: Show General Router Stats</p></div>
-<div class="paragraph"><p>-c, --connections
-: Show Connections</p></div>
-<div class="paragraph"><p>-l, --links
-: Show Router Links</p></div>
-<div class="paragraph"><p>-n, --nodes
-: Show Router Nodes</p></div>
-<div class="paragraph"><p>-a, --address
-: Show Router Addresses</p></div>
-<div class="paragraph"><p>-m, --memory
-: Show Router Memory Stats</p></div>
-<div class="paragraph"><p>--autolinks
-: Show Auto Links</p></div>
-<div class="paragraph"><p>--linkroutes
-: Show Link Routes</p></div>
-<div class="paragraph"><p>-v, --verbose
-: Show maximum detail</p></div>
-<div class="paragraph"><p>--log
-: Show recent log entries</p></div>
-<div class="paragraph"><p>--limit=LIMIT
-: Limit number of log entries</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_output_columns">OUTPUT COLUMNS</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_qdstat_c">qdstat -c</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-id
-</dt>
-<dd>
-<p>
-Unique connection identifier
-</p>
-</dd>
-<dt class="hdlist1">
-host
-</dt>
-<dd>
-<p>
-The hostname or internet address of the remotely connected AMQP container
-</p>
-</dd>
-<dt class="hdlist1">
-container
-</dt>
-<dd>
-<p>
-The container-name of the remotely connected AMQP container
-</p>
-</dd>
-<dt class="hdlist1">
-role
-</dt>
-<dd>
-<p>
-The configured role of the connection
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-normal - Normal connections from client to router
-</p>
-</li>
-<li>
-<p>
-inter-router - Connection between routers to form a network
-</p>
-</li>
-<li>
-<p>
-route-container - Connection to/from a Broker or other host to receive link-routes and waypoints
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-dir
-</dt>
-<dd>
-<p>
-The direction of connection establishment
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-in - The connection was initiated by the remote container
-</p>
-</li>
-<li>
-<p>
-out - The connection was initiated by this router
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-security
-</dt>
-<dd>
-<p>
-A description of the security/encryption in effect for this
-connection
-</p>
-</dd>
-<dt class="hdlist1">
-authentication
-</dt>
-<dd>
-<p>
-The method and user-id of the authenticated user for
-this connection
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_l">qdstat -l</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-type
-</dt>
-<dd>
-<p>
-Type of link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-router-control - An inter-router link that is reserved for control messages exchanged between routers
-</p>
-</li>
-<li>
-<p>
-inter-router - An inter-router link that is used for normal message-routed deliveries
-</p>
-</li>
-<li>
-<p>
-endpoint - A normal link to an external endpoint container
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-dir
-</dt>
-<dd>
-<p>
-The direction of message flow on the link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-in - Deliveries flow inbound to the router
-</p>
-</li>
-<li>
-<p>
-out - Deliveries flow outbound from the router
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-conn id
-</dt>
-<dd>
-<p>
-Unique identifier of the connection over which this link is
-attached
-</p>
-</dd>
-<dt class="hdlist1">
-id
-</dt>
-<dd>
-<p>
-Unique identifier of this link
-</p>
-</dd>
-<dt class="hdlist1">
-peer
-</dt>
-<dd>
-<p>
-For link-routed links, the unique identifier of the peer link. In
-link routing, an inbound link is paired with an outbound link
-</p>
-</dd>
-<dt class="hdlist1">
-class
-</dt>
-<dd>
-<p>
-Class of the address bound to the link
-</p>
-</dd>
-<dt class="hdlist1">
-addr
-</dt>
-<dd>
-<p>
-The address bound to the link
-</p>
-</dd>
-<dt class="hdlist1">
-phs
-</dt>
-<dd>
-<p>
-The phase of the address bound to the link
-</p>
-</dd>
-<dt class="hdlist1">
-cap
-</dt>
-<dd>
-<p>
-The capacity, in deliveries, of the link
-</p>
-</dd>
-<dt class="hdlist1">
-undel
-</dt>
-<dd>
-<p>
-The number of undelivered messages stored on the link’s FIFO
-</p>
-</dd>
-<dt class="hdlist1">
-unsettled
-</dt>
-<dd>
-<p>
-The number of unsettled deliveries being tracked by the link
-</p>
-</dd>
-<dt class="hdlist1">
-deliveries
-</dt>
-<dd>
-<p>
-The total number of deliveries that have transited this link
-</p>
-</dd>
-<dt class="hdlist1">
-admin
-</dt>
-<dd>
-<p>
-The administrative status of the link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-enabled - The link is enabled for normal operation
-</p>
-</li>
-<li>
-<p>
-disabled - The link is disabled and should be quiescing or stopped (not yet supported)
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-oper
-</dt>
-<dd>
-<p>
-The operational status of the link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-up - The link is operational
-</p>
-</li>
-<li>
-<p>
-down - The link is not attached
-</p>
-</li>
-<li>
-<p>
-quiescing - The link is in the process of quiescing (not yet supported)
-</p>
-</li>
-<li>
-<p>
-idle - The link has completed quiescing and is idle (not yet supported)
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-name
-</dt>
-<dd>
-<p>
-The link name (only shown if the -v option is provided)
-</p>
-</dd>
-</dl></div>
-<div class="sect3">
-<h4 id="_qdstat_n">qdstat -n</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-router-id
-</dt>
-<dd>
-<p>
-Identifier of the router
-</p>
-</dd>
-<dt class="hdlist1">
-next-hop
-</dt>
-<dd>
-<p>
-If this router is not a neighbor, identifies the next-hop neighbor used to reach this router
-</p>
-</dd>
-<dt class="hdlist1">
-link
-</dt>
-<dd>
-<p>
-Unique identifier of the link to the neighbor router
-</p>
-</dd>
-<dt class="hdlist1">
-cost
-</dt>
-<dd>
-<p>
-The topology cost to this remote router (with -v option only)
-</p>
-</dd>
-<dt class="hdlist1">
-neighbors
-</dt>
-<dd>
-<p>
-The list of neighbor routers (the router’s link-state) (with -v option only)
-</p>
-</dd>
-<dt class="hdlist1">
-valid-origins
-</dt>
-<dd>
-<p>
-The list of origin routers for which the best path to the listed router passes through this router (with -v option only)
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_a">qdstat -a</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-class
-</dt>
-<dd>
-<p>
-The class of the listed address
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-local - Address that is local to this router
-</p>
-</li>
-<li>
-<p>
-topo - Topological address used for router control messages
-</p>
-</li>
-<li>
-<p>
-router - A summary router address used to route messages to a remote router’s local addresses
-</p>
-</li>
-<li>
-<p>
-mobile - A mobile address for an attached consumer or producer
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-addr
-</dt>
-<dd>
-<p>
-The address text
-</p>
-</dd>
-<dt class="hdlist1">
-phs
-</dt>
-<dd>
-<p>
-For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.
-</p>
-</dd>
-<dt class="hdlist1">
-distrib
-</dt>
-<dd>
-<p>
-Distribution method used for this address
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-multicast - A copy of each message is delivered once to each consumer for the address
-</p>
-</li>
-<li>
-<p>
-closest - Each message is delivered to only one consumer for the address. The closest (lowest cost) consumer will be chosen. If there are multiple lowest-cost consumers, deliveries will be spread across those consumers.
-</p>
-</li>
-<li>
-<p>
-balanced - Each message is delivered to only one consumer for the address. The consumer with the fewest outstanding (unsettled) deliveries will be chosen. The cost of the route to the consumer is a threshold for delivery (i.e. higher cost consumers will only receive deliveries if closer consumers are backed up).
-</p>
-</li>
-<li>
-<p>
-flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-in-proc
-</dt>
-<dd>
-<p>
-The number of in-process consumers for this address
-</p>
-</dd>
-<dt class="hdlist1">
-local
-</dt>
-<dd>
-<p>
-The number of local (on this router) consumers for this address
-</p>
-</dd>
-<dt class="hdlist1">
-remote
-</dt>
-<dd>
-<p>
-The number of remote routers that have at least one consumer for this address
-</p>
-</dd>
-<dt class="hdlist1">
-cntnr
-</dt>
-<dd>
-<p>
-The number of locally attached containers that are destinations for link-routes on this address
-</p>
-</dd>
-<dt class="hdlist1">
-in
-</dt>
-<dd>
-<p>
-The number of deliveries for this address that entered the network on this router
-</p>
-</dd>
-<dt class="hdlist1">
-out
-</dt>
-<dd>
-<p>
-The number of deliveries for this address that exited the network on this router
-</p>
-</dd>
-<dt class="hdlist1">
-thru
-</dt>
-<dd>
-<p>
-The number of deliveries for this address that were forwarded to other routers
-</p>
-</dd>
-<dt class="hdlist1">
-to-proc
-</dt>
-<dd>
-<p>
-The number of deliveries for this address that were delivered to an in-process consumer
-</p>
-</dd>
-<dt class="hdlist1">
-from-proc
-</dt>
-<dd>
-<p>
-The number of deliveries for this address that were received from an in-process producer
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_linkroutes">qdstat --linkroutes</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-prefix
-</dt>
-<dd>
-<p>
-The prefix for matching addresses of routed links
-</p>
-</dd>
-<dt class="hdlist1">
-dir
-</dt>
-<dd>
-<p>
-The direction (from the router’s perspective) of matching links
-</p>
-</dd>
-<dt class="hdlist1">
-distrib
-</dt>
-<dd>
-<p>
-The distribution method used for routed links
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-linkBalanced - the only supported distribution for routed links
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-status
-</dt>
-<dd>
-<p>
-Operational status of the link route
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-active - Route is actively routing attaches (i.e. ready for use)
-</p>
-</li>
-<li>
-<p>
-inactive - Route is inactive because there is no local destination connected
-</p>
-</li>
-</ul></div>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qstat_autolinks">qstat --autolinks</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-addr
-</dt>
-<dd>
-<p>
-The address of the auto link
-</p>
-</dd>
-<dt class="hdlist1">
-dir
-</dt>
-<dd>
-<p>
-The direction of message flow for the auto link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-in - Messages flow in from the route-container to the router network
-</p>
-</li>
-<li>
-<p>
-out - Messages flow out to the route-container from the router network
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-phs
-</dt>
-<dd>
-<p>
-Phase of the address for this auto link
-</p>
-</dd>
-<dt class="hdlist1">
-link
-</dt>
-<dd>
-<p>
-Unique identifier of the link managed by this auto link
-</p>
-</dd>
-<dt class="hdlist1">
-status
-</dt>
-<dd>
-<p>
-The operational status of this auto link
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-inactive - There is no connected container for this auto link
-</p>
-</li>
-<li>
-<p>
-attaching - The link is attaching to the container
-</p>
-</li>
-<li>
-<p>
-failed - The link-attach failed
-</p>
-</li>
-<li>
-<p>
-active - The link is operational
-</p>
-</li>
-<li>
-<p>
-quiescing - The link is quiescing (not yet supported)
-</p>
-</li>
-<li>
-<p>
-idle - The link is idle (not yet supported)
-</p>
-</li>
-</ul></div>
-</dd>
-<dt class="hdlist1">
-lastErr
-</dt>
-<dd>
-<p>
-The description of the last attach failure that occurred on this auto link
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdstat.8.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdstat.8.html.in b/input/releases/qpid-dispatch-master/qdstat.8.html.in
index 529b962..9a8bd4c 100644
--- a/input/releases/qpid-dispatch-master/qdstat.8.html.in
+++ b/input/releases/qpid-dispatch-master/qdstat.8.html.in
@@ -1,815 +1,58 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdstat(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdstat(8) Manual Page
-</h1>
<h2>NAME</h2>
-<div class="sectionbody">
<p>qdstat -
show status and statistics for a running 'qdrouterd'
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdstat</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Shows status information about networks of Dispatch routers. It can display
-connections, network nodes and links, and router stats such as memory use.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>-g, --general
-: Show General Router Stats</p></div>
-<div class="paragraph"><p>-c, --connections
-: Show Connections</p></div>
-<div class="paragraph"><p>-l, --links
-: Show Router Links</p></div>
-<div class="paragraph"><p>-n, --nodes
-: Show Router Nodes</p></div>
-<div class="paragraph"><p>-a, --address
-: Show Router Addresses</p></div>
-<div class="paragraph"><p>-m, --memory
-: Show Router Memory Stats</p></div>
-<div class="paragraph"><p>--autolinks
-: Show Auto Links</p></div>
-<div class="paragraph"><p>--linkroutes
-: Show Link Routes</p></div>
-<div class="paragraph"><p>-v, --verbose
-: Show maximum detail</p></div>
-<div class="paragraph"><p>--log
-: Show recent log entries</p></div>
-<div class="paragraph"><p>--limit=LIMIT
-: Limit number of log entries</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_output_columns">OUTPUT COLUMNS</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_qdstat_c">qdstat -c</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdstat</strong> [<b>OPTIONS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>Shows status information about networks of Dispatch routers. It can display
+connections, network nodes and links, and router stats such as memory use.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-h, --help
+: show this help message and exit</p>
+<p>--version
+: Print version and exit.</p>
+<p>-g, --general
+: Show General Router Stats</p>
+<p>-c, --connections
+: Show Connections</p>
+<p>-l, --links
+: Show Router Links</p>
+<p>-n, --nodes
+: Show Router Nodes</p>
+<p>-a, --address
+: Show Router Addresses</p>
+<p>-m, --memory
+: Show Router Memory Stats</p>
+<p>--autolinks
+: Show Auto Links</p>
+<p>--linkroutes
+: Show Link Routes</p>
+<p>-v, --verbose
+: Show maximum detail</p>
+<p>--log
+: Show recent log entries</p>
+<p>--limit=LIMIT
+: Limit number of log entries</p>
+<h3><a name="_connection_options"></a>Connection Options</h3>
+<p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default 0.0.0.0)</p>
+<p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+<h2><a name="_output_columns"></a>OUTPUT COLUMNS</h2>
+<h3><a name="_qdstat_c"></a>qdstat -c</h3>
+<dl>
+<dt>
id
</dt>
<dd>
@@ -817,7 +60,7 @@ id
Unique connection identifier
</p>
</dd>
-<dt class="hdlist1">
+<dt>
host
</dt>
<dd>
@@ -825,7 +68,7 @@ host
The hostname or internet address of the remotely connected AMQP container
</p>
</dd>
-<dt class="hdlist1">
+<dt>
container
</dt>
<dd>
@@ -833,14 +76,14 @@ container
The container-name of the remotely connected AMQP container
</p>
</dd>
-<dt class="hdlist1">
+<dt>
role
</dt>
<dd>
<p>
The configured role of the connection
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
normal - Normal connections from client to router
@@ -856,16 +99,16 @@ inter-router - Connection between routers to form a network
route-container - Connection to/from a Broker or other host to receive link-routes and waypoints
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of connection establishment
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - The connection was initiated by the remote container
@@ -876,9 +119,9 @@ in - The connection was initiated by the remote container
out - The connection was initiated by this router
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
security
</dt>
<dd>
@@ -887,7 +130,7 @@ A description of the security/encryption in effect for this
connection
</p>
</dd>
-<dt class="hdlist1">
+<dt>
authentication
</dt>
<dd>
@@ -896,19 +139,17 @@ The method and user-id of the authenticated user for
this connection
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_l">qdstat -l</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_l"></a>qdstat -l</h3>
+<dl>
+<dt>
type
</dt>
<dd>
<p>
Type of link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
router-control - An inter-router link that is reserved for control messages exchanged between routers
@@ -924,16 +165,16 @@ inter-router - An inter-router link that is used for normal message-routed deliv
endpoint - A normal link to an external endpoint container
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of message flow on the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - Deliveries flow inbound to the router
@@ -944,9 +185,9 @@ in - Deliveries flow inbound to the router
out - Deliveries flow outbound from the router
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
conn id
</dt>
<dd>
@@ -955,7 +196,7 @@ Unique identifier of the connection over which this link is
attached
</p>
</dd>
-<dt class="hdlist1">
+<dt>
id
</dt>
<dd>
@@ -963,7 +204,7 @@ id
Unique identifier of this link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
peer
</dt>
<dd>
@@ -972,7 +213,7 @@ For link-routed links, the unique identifier of the peer link. In
link routing, an inbound link is paired with an outbound link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
class
</dt>
<dd>
@@ -980,7 +221,7 @@ class
Class of the address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
addr
</dt>
<dd>
@@ -988,7 +229,7 @@ addr
The address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -996,7 +237,7 @@ phs
The phase of the address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cap
</dt>
<dd>
@@ -1004,7 +245,7 @@ cap
The capacity, in deliveries, of the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
undel
</dt>
<dd>
@@ -1012,7 +253,7 @@ undel
The number of undelivered messages stored on the link’s FIFO
</p>
</dd>
-<dt class="hdlist1">
+<dt>
unsettled
</dt>
<dd>
@@ -1020,7 +261,7 @@ unsettled
The number of unsettled deliveries being tracked by the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
deliveries
</dt>
<dd>
@@ -1028,14 +269,14 @@ deliveries
The total number of deliveries that have transited this link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
admin
</dt>
<dd>
<p>
The administrative status of the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
enabled - The link is enabled for normal operation
@@ -1046,16 +287,16 @@ enabled - The link is enabled for normal operation
disabled - The link is disabled and should be quiescing or stopped (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
oper
</dt>
<dd>
<p>
The operational status of the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
up - The link is operational
@@ -1076,9 +317,9 @@ quiescing - The link is in the process of quiescing (not yet supported)
idle - The link has completed quiescing and is idle (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
name
</dt>
<dd>
@@ -1086,11 +327,10 @@ name
The link name (only shown if the -v option is provided)
</p>
</dd>
-</dl></div>
-<div class="sect3">
-<h4 id="_qdstat_n">qdstat -n</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h4><a name="_qdstat_n"></a>qdstat -n</h4>
+<dl>
+<dt>
router-id
</dt>
<dd>
@@ -1098,7 +338,7 @@ router-id
Identifier of the router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
next-hop
</dt>
<dd>
@@ -1106,7 +346,7 @@ next-hop
If this router is not a neighbor, identifies the next-hop neighbor used to reach this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
link
</dt>
<dd>
@@ -1114,7 +354,7 @@ link
Unique identifier of the link to the neighbor router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cost
</dt>
<dd>
@@ -1122,7 +362,7 @@ cost
The topology cost to this remote router (with -v option only)
</p>
</dd>
-<dt class="hdlist1">
+<dt>
neighbors
</dt>
<dd>
@@ -1130,7 +370,7 @@ neighbors
The list of neighbor routers (the router’s link-state) (with -v option only)
</p>
</dd>
-<dt class="hdlist1">
+<dt>
valid-origins
</dt>
<dd>
@@ -1138,20 +378,17 @@ valid-origins
The list of origin routers for which the best path to the listed router passes through this router (with -v option only)
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_a">qdstat -a</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_a"></a>qdstat -a</h3>
+<dl>
+<dt>
class
</dt>
<dd>
<p>
The class of the listed address
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
local - Address that is local to this router
@@ -1172,9 +409,9 @@ router - A summary router address used to route messages to a remote router̵
mobile - A mobile address for an attached consumer or producer
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
addr
</dt>
<dd>
@@ -1182,7 +419,7 @@ addr
The address text
</p>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -1190,14 +427,14 @@ phs
For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
distrib
</dt>
<dd>
<p>
Distribution method used for this address
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
multicast - A copy of each message is delivered once to each consumer for the address
@@ -1218,9 +455,9 @@ balanced - Each message is delivered to only one consumer for the address. The
flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
in-proc
</dt>
<dd>
@@ -1228,7 +465,7 @@ in-proc
The number of in-process consumers for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
local
</dt>
<dd>
@@ -1236,7 +473,7 @@ local
The number of local (on this router) consumers for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
remote
</dt>
<dd>
@@ -1244,7 +481,7 @@ remote
The number of remote routers that have at least one consumer for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cntnr
</dt>
<dd>
@@ -1252,7 +489,7 @@ cntnr
The number of locally attached containers that are destinations for link-routes on this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
in
</dt>
<dd>
@@ -1260,7 +497,7 @@ in
The number of deliveries for this address that entered the network on this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
out
</dt>
<dd>
@@ -1268,7 +505,7 @@ out
The number of deliveries for this address that exited the network on this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
thru
</dt>
<dd>
@@ -1276,7 +513,7 @@ thru
The number of deliveries for this address that were forwarded to other routers
</p>
</dd>
-<dt class="hdlist1">
+<dt>
to-proc
</dt>
<dd>
@@ -1284,7 +521,7 @@ to-proc
The number of deliveries for this address that were delivered to an in-process consumer
</p>
</dd>
-<dt class="hdlist1">
+<dt>
from-proc
</dt>
<dd>
@@ -1292,12 +529,10 @@ from-proc
The number of deliveries for this address that were received from an in-process producer
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_linkroutes">qdstat --linkroutes</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_linkroutes"></a>qdstat --linkroutes</h3>
+<dl>
+<dt>
prefix
</dt>
<dd>
@@ -1305,7 +540,7 @@ prefix
The prefix for matching addresses of routed links
</p>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
@@ -1313,29 +548,29 @@ dir
The direction (from the router’s perspective) of matching links
</p>
</dd>
-<dt class="hdlist1">
+<dt>
distrib
</dt>
<dd>
<p>
The distribution method used for routed links
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
linkBalanced - the only supported distribution for routed links
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
status
</dt>
<dd>
<p>
Operational status of the link route
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
active - Route is actively routing attaches (i.e. ready for use)
@@ -1346,14 +581,12 @@ active - Route is actively routing attaches (i.e. ready for use)
inactive - Route is inactive because there is no local destination connected
</p>
</li>
-</ul></div>
+</ul>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qstat_autolinks">qstat --autolinks</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qstat_autolinks"></a>qstat --autolinks</h3>
+<dl>
+<dt>
addr
</dt>
<dd>
@@ -1361,14 +594,14 @@ addr
The address of the auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of message flow for the auto link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - Messages flow in from the route-container to the router network
@@ -1379,9 +612,9 @@ in - Messages flow in from the route-container to the router network
out - Messages flow out to the route-container from the router network
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -1389,7 +622,7 @@ phs
Phase of the address for this auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
link
</dt>
<dd>
@@ -1397,14 +630,14 @@ link
Unique identifier of the link managed by this auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
status
</dt>
<dd>
<p>
The operational status of this auto link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
inactive - There is no connected container for this auto link
@@ -1435,9 +668,9 @@ quiescing - The link is quiescing (not yet supported)
idle - The link is idle (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
lastErr
</dt>
<dd>
@@ -1445,23 +678,7 @@ lastErr
The description of the last attach failure that occurred on this auto link
</p>
</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd(8)</b>, <b>qdmanage(8)</b>, <b>qdrouterd.conf(5)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/scripts/gen-dispatch-release-books
----------------------------------------------------------------------
diff --git a/scripts/gen-dispatch-release-books b/scripts/gen-dispatch-release-books
index 56b2f56..5447259 100755
--- a/scripts/gen-dispatch-release-books
+++ b/scripts/gen-dispatch-release-books
@@ -31,19 +31,14 @@ def gen_books_and_man(release, source_dir, output_dir):
build_doc = join(build_dir, "doc")
- # Rename .html to .html.in to get site style.
- for f in list_dir(build_doc, "*.html"):
- if not f == "index.html": # Use gen-dispatch-release-page index.
- copy(join(build_doc, f), join(output_dir, f) + ".in")
-
- # Copy other doc files.
- for f in list_dir(build_doc, "*.html", "*.pdf", "*.png"):
- if not f == "index.html": # Use gen-dispatch-release-page index.
+ # .html.in files are raw HTML bodies, the render script will apply the site style.
+ for f in list_dir(build_doc, "*.html.in", "*.pdf", "*.png"):
+ if not f == "index.html.in": # Use gen-dispatch-release-page index.
copy(join(build_doc, f), join(output_dir, f))
## Now do stuff ##
release, issues_release, source_release, release_dir, checkout_dir = setup_release_script()
-source_dir = export_release_from_git("dispatch", source_release)
+source_dir = checkout_dir or export_release_from_git("dispatch", source_release)
gen_books_and_man(release, source_dir, release_dir)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[10/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/book.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/book.html b/content/releases/qpid-dispatch-master/book.html
index a27fac9..b12e5b2 100644
--- a/content/releases/qpid-dispatch-master/book.html
+++ b/content/releases/qpid-dispatch-master/book.html
@@ -21,7 +21,7 @@
-->
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
- <title>Qpid Dispatch Router Book - Apache Qpid™</title>
+ <title>1. Introduction - Apache Qpid™</title>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<link rel="stylesheet" href="/site.css" type="text/css" async="async"/>
@@ -111,765 +111,23 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
</div>
<div id="-middle" class="panel">
- <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>Qpid Dispatch Router Book</li></ul>
+ <ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>1. Introduction</li></ul>
<div id="-middle-content">
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>Qpid Dispatch Router Book</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install(2);
-/*]]>*/
-</script>
-</head>
-<body class="book">
-<div id="header">
-<h1>Qpid Dispatch Router Book</h1>
-<div id="toc">
- <div id="toctitle">Table of Contents</div>
- <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="introduction">1. Introduction</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="overview">1.1. Overview</h3>
-<div class="paragraph"><p>The Dispatch router is an AMQP message router that provides
+ <hr>
+<h2><a name="introduction"></a>1. Introduction</h2>
+<h3><a name="overview"></a>1.1. Overview</h3>
+<p>The Dispatch router is an AMQP message router that provides
advanced interconnect capabilities. It allows flexible routing of
messages between any AMQP-enabled endpoints, whether they be clients,
servers, brokers or any other entity that can send or receive standard
-AMQP messages.</p></div>
-<div class="paragraph"><p>A messaging client can make a single AMQP connection into a messaging
+AMQP messages.</p>
+<p>A messaging client can make a single AMQP connection into a messaging
bus built of Dispatch routers and, over that connection, exchange
messages with one or more message brokers, and at the same time exchange
messages directly with other endpoints without involving a broker at
-all.</p></div>
-<div class="paragraph"><p>The router is an intermediary for messages but it is <em>not</em> a broker. It
+all.</p>
+<p>The router is an intermediary for messages but it is <em>not</em> a broker. It
does not <em>take responsibility for</em> messages. It will, however, propagate
settlement and disposition across a network such that delivery
guarantees are met. In other words: the router network will deliver the
@@ -879,14 +137,14 @@ the same path. This means that <em>responsibility</em> for the message is
transfered from the original sender to the ultimate receiver <em>as if
they were directly connected</em>. However this is done via a flexible
network that allows highly configurable routing of the message
-transparent to both sender and receiver.</p></div>
-<div class="paragraph"><p>There are some patterns where this enables "brokerless messaging"
+transparent to both sender and receiver.</p>
+<p>There are some patterns where this enables "brokerless messaging"
approaches that are preferable to brokered approaches. In other cases a
broker is essential (in particular where you need the separation of
responsibility and/or the buffering provided by store-and-forward) but a
dispatch network can still be useful to tie brokers and clients together
-into patterns that are difficult with a single broker.</p></div>
-<div class="paragraph"><p>For a "brokerless" example, consider the common brokered implementation
+into patterns that are difficult with a single broker.</p>
+<p>For a "brokerless" example, consider the common brokered implementation
of the request-response pattern, a client puts a request on a queue and
then waits for a reply on another queue. In this case the broker can be
a hindrance - the client may want to know immediatly if there is nobody
@@ -895,8 +153,8 @@ discover this. With a dispatch network, the client can be informed
immediately if its message cannot be delivered because nobody is
listening. When the client receives acknowledgement of the request it
knows not just that it is sitting on a queue, but that it has actually
-been received by the server.</p></div>
-<div class="paragraph"><p>For an exampe of using dispatch to enhance the use of brokers, consider
+been received by the server.</p>
+<p>For an exampe of using dispatch to enhance the use of brokers, consider
using an array of brokers to implement a scalable distributed work
queue. A dispatch network can make this appear as a single queue, with
senders publishing to a single address and receivers subscribing to a
@@ -908,8 +166,8 @@ pattern with brokers alone. If a receiver is connected to a broker that
has no messages, but there are messages on another broker, you have to
somehow transfer them or leave them "stuck". With a dispatch network,
<em>all</em> the receivers are connected to <em>all</em> the brokers. If there is a
-message anywhere it can be delivered to any receiver.</p></div>
-<div class="paragraph"><p>The router is meant to be deployed in topologies of multiple routers,
+message anywhere it can be delivered to any receiver.</p>
+<p>The router is meant to be deployed in topologies of multiple routers,
preferably with redundant paths. It uses link-state routing protocols
and algorithms (similar to OSPF or IS-IS from the networking world) to
calculate the best path from every point to every other point and to
@@ -919,12 +177,10 @@ continued connectivity in the face of system or network failure. Because
it never takes responsibility for messages it is effectively stateless.
Messages not delivered to their final destination will not be
acknowledged to the sender and therefore the sender can re-send such
-messages if it is disconnected from the network.</p></div>
-</div>
-<div class="sect2">
-<h3 id="benefits">1.2. Benefits</h3>
-<div class="paragraph"><p>Simplifies connectivity</p></div>
-<div class="ulist"><ul>
+messages if it is disconnected from the network.</p>
+<h3><a name="benefits"></a>1.2. Benefits</h3>
+<p>Simplifies connectivity</p>
+<ul>
<li>
<p>
An endpoint can do all of its messaging through a single transport
@@ -936,9 +192,9 @@ connection
Avoid opening holes in firewalls for incoming connections
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>Provides messaging connectivity where there is no TCP/IP connectivity</p></div>
-<div class="ulist"><ul>
+</ul>
+<p>Provides messaging connectivity where there is no TCP/IP connectivity</p>
+<ul>
<li>
<p>
A server or broker can be in a private IP network (behind a NAT
@@ -946,9 +202,9 @@ firewall) and be accessible by messaging endpoints in other networks
(learn more).
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>Simplifies reliability</p></div>
-<div class="ulist"><ul>
+</ul>
+<p>Simplifies reliability</p>
+<ul>
<li>
<p>
Reliability and availability are provided using redundant topology,
@@ -965,29 +221,27 @@ Reliable end-to-end messaging without persistent stores
Use a message broker only when you need store-and-forward semantics
</p>
</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="features">1.3. Features</h3>
-<div class="ulist"><ul>
+</ul>
+<h3><a name="features"></a>1.3. Features</h3>
+<ul>
<li>
<p>
Can be deployed stand-alone or in a network of routers
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Supports arbitrary network topology - no restrictions on redundancy
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Automatic route computation - adjusts quickly to changes in topology
</p>
</li>
-</ul></div>
+</ul>
</li>
-</ul></div>
+</ul>
</li>
<li>
<p>
@@ -999,50 +253,40 @@ Provides remote access to brokers or other AMQP servers
Security
</p>
</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="using-qpid-dispatch">2. Using Qpid Dispatch</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="configuration">2.1. Configuration</h3>
-<div class="paragraph"><p>The default configuration file is installed in
-<em>install-prefix/etc/qpid-dispatch/qdrouterd.conf</em>. This configuration file will
+</ul>
+<hr>
+<h2><a name="using-qpid-dispatch"></a>2. Using Qpid Dispatch</h2>
+<h3><a name="configuration"></a>2.1. Configuration</h3>
+<p>The default configuration file is installed in
+<em>/usr/local/etc/qpid-dispatch/qdrouterd.conf</em>. 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></div>
-<div class="paragraph"><p>To run the router, invoke the executable: qdrouterd [-c my-config-file]</p></div>
-<div class="paragraph"><p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
-page.</p></div>
-</div>
-<div class="sect2">
-<h3 id="tools">2.2. Tools</h3>
-<div class="sect3">
-<h4 id="qdstat">2.2.1. qdstat</h4>
-<div class="paragraph"><p><em>qdstat</em> is a command line tool that lets you view the status of a
+configuration to load.</p>
+<p>To run the router, invoke the executable: <code>qdrouterd [-c my-config-file]</code></p>
+<p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
+page.</p>
+<h3><a name="tools"></a>2.2. Tools</h3>
+<h4><a name="qdstat"></a>2.2.1. qdstat</h4>
+<p><em>qdstat</em> is a command line tool that lets you view the status of a
Dispatch Router. The following options are useful for seeing what the
-router is doing:</p></div>
-<div class="tableblock">
+router is doing:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="17%" />
-<col width="83%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Option</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="17%" valign="top"><em>Option</em> </th>
+<th align="left" width="83%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">-l</p></td>
-<td align="left" valign="top"><p class="table">Print a list of AMQP links attached to the router. Links are
+<td align="left" width="17%" valign="top"><p>-l</p></td>
+<td align="left" width="83%" valign="top"><p>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
@@ -1050,76 +294,65 @@ router. Router links are attached to other routers in a network of
routbers.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-a</p></td>
-<td align="left" valign="top"><p class="table">Print a list of addresses known to the router.</p></td>
+<td align="left" width="17%" valign="top"><p>-a</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of addresses known to the router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-n</p></td>
-<td align="left" valign="top"><p class="table">Print a list of known routers in the network.</p></td>
+<td align="left" width="17%" valign="top"><p>-n</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of known routers in the network.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-c</p></td>
-<td align="left" valign="top"><p class="table">Print a list of connections to the router.</p></td>
+<td align="left" width="17%" valign="top"><p>-c</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of connections to the router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">--autolinks</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configured auto-links.</p></td>
+<td align="left" width="17%" valign="top"><p>--autolinks</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of configured auto-links.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">--linkroutes</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configures link-routes.</p></td>
+<td align="left" width="17%" valign="top"><p>--linkroutes</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of configures link-routes.</p></td>
</tr>
</tbody>
</table>
</div>
-<div class="paragraph"><p>For complete details see the <em>qdstat(8)</em> man page and the output of
-<code>qdstat --help</code>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="qdmanage">2.2.2. qdmanage</h4>
-<div class="paragraph"><p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
+<p>For complete details see the <em>qdstat(8)</em> man page and the output of
+<code>qdstat --help</code>.</p>
+<h4><a name="qdmanage"></a>2.2.2. qdmanage</h4>
+<p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
to not only view but modify the configuration of a running dispatch
-router.</p></div>
-<div class="paragraph"><p>For example you can query all the connection entities in the router:</p></div>
-<div class="listingblock">
-<div class="content">
+router.</p>
+<p>For example you can query all the connection entities in the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage query --type connection</code></pre>
-</div></div>
-<div class="paragraph"><p>To enable logging debug and higher level messages by default:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>To enable logging debug and higher level messages by default:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage update log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="paragraph"><p>In fact, everything that can be configured in the configuration file can
+</td></tr></table>
+<p>In fact, everything that can be configured in the configuration file can
also be created in a running router via management. For example to
-create a new listener in a running router:</p></div>
-<div class="listingblock">
-<div class="content">
+create a new listener in a running router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage create type=listener port=5555</code></pre>
-</div></div>
-<div class="paragraph"><p>Now you can connect to port 5555, for exampple:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>Now you can connect to port 5555, for exampple:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage query -b localhost:5555 --type listener</code></pre>
-</div></div>
-<div class="paragraph"><p>For complete details see the <em>qdmanage(8)</em> man page and the output of
+</td></tr></table>
+<p>For complete details see the <em>qdmanage(8)</em> man page and the output of
<code>qdmanage --help</code>. Also for details of what can be configured see the
-<em>qdrouterd.conf(5)</em> man page.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="basic-usage-and-examples">2.3. Basic Usage and Examples</h3>
-<div class="sect3">
-<h4 id="standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</h4>
-<div class="paragraph"><p>The router can operate stand-alone or as a node in a network of routers.
+<em>qdrouterd.conf(5)</em> man page.</p>
+<h3><a name="basic-usage-and-examples"></a>2.3. Basic Usage and Examples</h3>
+<h4><a name="standalone-and-interior-modes"></a>2.3.1. Standalone and Interior Modes</h4>
+<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></div>
-<div class="paragraph"><p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
-like the following:</p></div>
-<div class="listingblock">
-<div class="content">
+endpoints.</p>
+<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1129,16 +362,15 @@ Router Addresses
mobile $management 0 closest 1 0 0 0 1 0 0 1 0
local $management closest 1 0 0 0 0 0 0 0 0
local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that there are a number of known addresses. <em>$management</em> is the
+</td></tr></table>
+<p>Note that there are a number of known addresses. <em>$management</em> is the
address of the router’s embedded management agent.
<em>temp.1GThUllfR7N+BDP</em> is the temporary reply-to address of the <em>qdstat</em>
-client making requests to the agent.</p></div>
-<div class="paragraph"><p>If you change the mode to interior and restart the processs, the same
+client making requests to the agent.</p>
+<p>If you change the mode to interior and restart the processs, the same
command will yield additional addresses which are used for inter-router
-communication:</p></div>
-<div class="listingblock">
-<div class="content">
+communication:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1153,25 +385,21 @@ Router Addresses
local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="mobile-subscribers">2.3.2. Mobile Subscribers</h4>
-<div class="paragraph"><p>The term "mobile subscriber" simply refers to the fact that a client may
+</td></tr></table>
+<h4><a name="mobile-subscribers"></a>2.3.2. Mobile Subscribers</h4>
+<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></div>
-<div class="paragraph"><p>To illustrate a subscription on a stand-alone router, you can use the
+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>simple_recv.py</em>
-example receiver:</p></div>
-<div class="listingblock">
-<div class="content">
+example receiver:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python ./simple_recv.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-<div class="paragraph"><p>This command creates a receiving link subscribed to the specified
-address. To verify the subscription:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1182,24 +410,20 @@ Router Addresses
local $management closest 1 0 0 0 0 0 0 0 0
mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>You can then, in a separate command window, run a sender to produce
-messages to that address:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python ./simple_send.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-reply-to">2.3.3. Dynamic Reply-To</h4>
-<div class="paragraph"><p>Dynamic reply-to can be used to obtain a reply-to address that routes
+</td></tr></table>
+<h4><a name="dynamic-reply-to"></a>2.3.3. Dynamic Reply-To</h4>
+<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></div>
-<div class="listingblock">
-<div class="content">
+routers' management addresses.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>#include <qpid/messaging/Address.h>
#include <qpid/messaging/Connection.h>
#include <qpid/messaging/Message.h>
@@ -1240,11 +464,10 @@ int main() {
connection.close();
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The equivalent program written in Python against the Proton Messenger
-API:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>The equivalent program written in Python against the Proton Messenger
+API:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>from proton import Messenger, Message
def main():
@@ -1275,14 +498,11 @@ def main():
messenger.stop()
main()</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="link-routing">2.4. Link Routing</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.4. This feature was
-significantly updated in Qpid Dispatch 0.6.</p></div>
-<div class="paragraph"><p>Link-routing is an alternative strategy for routing messages across a
+</td></tr></table>
+<h3><a name="link-routing"></a>2.4. Link Routing</h3>
+<p>This feature was introduced in Qpid Dispatch 0.4. This feature was
+significantly updated in Qpid Dispatch 0.6.</p>
+<p>Link-routing is an alternative strategy for routing messages across a
network of routers. With the existing message-routing strategy, each
router makes a routing decision on a per-message basis when the message
is delivered. Link-routing is different because it makes routing
@@ -1290,18 +510,17 @@ decisions when link-attach frames arrive. A link is effectively chained
across the network of routers from the establishing node to the
destination node. Once the link is established, the transfer of message
deliveries, flow frames, and dispositions is performed across the routed
-link.</p></div>
-<div class="paragraph"><p>The main benefit to link-routing is that endpoints can use the full link
+link.</p>
+<p>The main benefit to link-routing is that endpoints can use the full link
protocol to interact with other endpoints in far-flung parts of the
network. For example, a client can establish a receiver across the
network to a queue on a remote broker and use link credit to control
the flow of messages from the broker. Similarly, a receiver can
establish a link to a topic on a remote broker using a server-side
-filter.</p></div>
-<div class="paragraph"><p>Why would one want to do this? One reason is to provide client
-isolation. A network like the following can be deployed:</p></div>
-<div class="listingblock">
-<div class="content">
+filter.</p>
+<p>Why would one want to do this? One reason is to provide client
+isolation. A network like the following can be deployed:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code> Public Network
+-----------------+
| +-----+ |
@@ -1321,29 +540,27 @@ isolation. A network like the following can be deployed:</p></div>
| | | |
| | | |
+-----------------+ +-----------------+</code></pre>
-</div></div>
-<div class="paragraph"><p>The clients in Private Net B can be constrained (by firewall policy)
+</td></tr></table>
+<p>The clients in Private Net B can be constrained (by firewall policy)
to only connect to the Router in their own network. Using
link-routing, these clients can access queues, topics, and other AMQP
-services that are in the Public Network or even in Private Net A.</p></div>
-<div class="paragraph"><p>For example, The router Ra can be configured to expose queues in
+services that are in the Public Network or even in Private Net A.</p>
+<p>For example, The router Ra can be configured to expose queues in
broker B2 to the network. Client C1 can then establish a connection
to Rb, the local router, open a subscribing link to "b2.event-queue",
-and receive messages stored on that queue in broker B2.</p></div>
-<div class="paragraph"><p>C1 is unable to create a TCP/IP connection to B1 because of its
+and receive messages stored on that queue in broker B2.</p>
+<p>C1 is unable to create a TCP/IP connection to B1 because of its
isolation (and because B2 is itself in a private network). However, with
-link routing, C1 can interact with B2 using the AMQP link protocol.</p></div>
-<div class="paragraph"><p>Note that in this case, neither C1 nor B2 have been modified in any way
+link routing, C1 can interact with B2 using the AMQP link protocol.</p>
+<p>Note that in this case, neither C1 nor B2 have been modified in any way
and neither need be aware of the fact that there is a message-router
-network between them.</p></div>
-<div class="sect3">
-<h4 id="link-routing-configuration">2.4.1. Configuration</h4>
-<div class="paragraph"><p>Starting with the configured topology shown above, how is link-routing
-configured to support the example described above?</p></div>
-<div class="paragraph"><p>First, router Ra needs to be told how to make a connection to the broker
-B2:</p></div>
-<div class="listingblock">
-<div class="content">
+network between them.</p>
+<h4><a name="link-routing-configuration"></a>2.4.1. Configuration</h4>
+<p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p>
+<p>First, router Ra needs to be told how to make a connection to the broker
+B2:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker
role: route-container
@@ -1351,13 +568,12 @@ B2:</p></div>
port: <B2-port>
saslMechanisms: ANONYMOUS
}</code></pre>
-</div></div>
-<div class="paragraph"><p>This <em>route-container</em> connector tells the router how to connect to an
+</td></tr></table>
+<p>This <em>route-container</em> connector tells the router how to connect to an
external AMQP container when it is needed. The name "broker" will be
-used later to refer to this connection.</p></div>
-<div class="paragraph"><p>Now, the router must be configured to route certain addresses to B2:</p></div>
-<div class="listingblock">
-<div class="content">
+used later to refer to this connection.</p>
+<p>Now, the router must be configured to route certain addresses to B2:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>linkRoute {
prefix: b2
dir: in
@@ -1369,18 +585,18 @@ linkRoute {
dir: out
connection: broker
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The linkRoute tells router Ra that any sender or receiver that is
+</td></tr></table>
+<p>The linkRoute tells router Ra that any sender or receiver that is
attached with a target or source (respectively) whos address begins with
"b2", should be routed to the broker B2 (via the route-container
-connector).</p></div>
-<div class="paragraph"><p>Note that receiving and sending links are configured and routed
+connector).</p>
+<p>Note that receiving and sending links are configured and routed
separately. This allows configuration of link routes for listeners only
or senders only. A direction of "in" matches client senders (i.e. links
that carry messages inbound to the router network). Direction "out"
-matches client receivers.</p></div>
-<div class="paragraph"><p>Examples of addresses that "begin with <em>b2</em>" include:</p></div>
-<div class="ulist"><ul>
+matches client receivers.</p>
+<p>Examples of addresses that "begin with <em>b2</em>" include:</p>
+<ul>
<li>
<p>
b2
@@ -1396,44 +612,40 @@ b2.queues
b2.queues.app1
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>When the route-container connector is configured, router Ra establishes
+</ul>
+<p>When the route-container connector is configured, router Ra establishes
a connection to the broker. Once the connection is open, Ra tells the
other routers (Rp and Rb) that it is a valid destination for link-routes
to the "b2" prefix. This means that sender or receiver links attached to
Rb or Rp will be routed via the shortest path to Ra where they are then
-routed outbound to the broker B2.</p></div>
-<div class="paragraph"><p>On Rp and Rb, it is advisable to add the identical configuration. It is
+routed outbound to the broker B2.</p>
+<p>On Rp and Rb, it is advisable to add the identical configuration. It is
permissible for a linkRoute configuration to reference a connection that
-does not exist.</p></div>
-<div class="paragraph"><p>This configuration tells the routers that link-routing is intended to be
+does not exist.</p>
+<p>This configuration tells the routers that link-routing is intended to be
available for targets and sources starting with "b2". This is important
because it is possible that B2 might be unavailable or shut off. If B2
is unreachable, Ra will not advertize itself as a destination for "b2"
and the other routers might never know that "b2" was intended for
-link-routing.</p></div>
-<div class="paragraph"><p>The above configuration allows Rb and Rp to reject attaches that should
+link-routing.</p>
+<p>The above configuration allows Rb and Rp to reject attaches that should
be routed to B2 with an error message that indicates that there is no
-route available to the destination.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="indirect-waypoints-and-auto-links">2.5. Indirect Waypoints and Auto-Links</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+route available to the destination.</p>
+<h3><a name="indirect-waypoints-and-auto-links"></a>2.5. Indirect Waypoints and Auto-Links</h3>
+<p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
improvement on an earlier somewhat experimental feature called
-Waypoints.</p></div>
-<div class="paragraph"><p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
+Waypoints.</p>
+<p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
actively attach a link to a node on an external AMQP container. The
obvious application for this feature is to route messages through a
-queue on a broker, but other applications are possible as well.</p></div>
-<div class="paragraph"><p>An auto-link manages the lifecycle of one AMQP link. If messages are to
+queue on a broker, but other applications are possible as well.</p>
+<p>An auto-link manages the lifecycle of one AMQP link. If messages are to
be routed to and from a queue on a broker, then two auto-links are
needed: one for sending messages to the queue and another for receiving
messages from the queue. The container to which an auto-link attempts to
-attach may be identified in one of two ways:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="ulist"><ul>
+attach may be identified in one of two ways:</p>
+<blockquote>
+<ul>
<li>
<p>
The name of the connector/listener that resulted in the connection of
@@ -1445,16 +657,14 @@ the container, or
The AMQP container-id of the remote container.
</p>
</li>
-</ul></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="sect3">
-<h4 id="queue-waypoint-example">2.5.1. Queue Waypoint Example</h4>
-<div class="paragraph"><p>Here is an example configuration for routing messages deliveries through
-a pair of queues on a broker:</p></div>
-<div class="listingblock">
-<div class="content">
+</ul>
+<p align="right">
+</p>
+</blockquote>
+<h4><a name="queue-waypoint-example"></a>2.5.1. Queue Waypoint Example</h4>
+<p>Here is an example configuration for routing messages deliveries through
+a pair of queues on a broker:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker
role: route-container
@@ -1491,15 +701,14 @@ autoLink {
dir: out
connection: broker
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
+</td></tr></table>
+<p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
for routing messages through queues via autolinks. The four <code>autoLink</code> entities
identify the head and tail of two queues on the broker that will be connected
-via auto-links.</p></div>
-<div class="paragraph"><p>If there is no broker connected, the auto-links shall remain
-<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p></div>
-<div class="listingblock">
-<div class="content">
+via auto-links.</p>
+<p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat --autolinks
AutoLinks
addr dir phase link status lastErr
@@ -1508,11 +717,10 @@ AutoLinks
queue.first out 0 inactive
queue.second in 1 inactive
queue.second out 0 inactive</code></pre>
-</div></div>
-<div class="paragraph"><p>If a broker comes online with a queue called <em>queue.first</em>, the
-auto-links will attempt to activate:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat --autolinks
AutoLinks
addr dir phase link status lastErr
@@ -1521,67 +729,60 @@ AutoLinks
queue.first out 0 7 active
queue.second in 1 failed Node not found: queue.second
queue.second out 0 failed Node not found: queue.second</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that two of the auto-links are in <em>failed</em> state because the queue
-does not exist on the broker.</p></div>
-<div class="paragraph"><p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
-three messages to <em>queue.first</em> via the router:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>Note that two of the auto-links are in <em>failed</em> state because the queue
+does not exist on the broker.</p>
+<p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
+three messages to <em>queue.first</em> via the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python simple_send.py -a 127.0.0.1/queue.first -m3
all messages confirmed</code></pre>
-</div></div>
-<div class="paragraph"><p>and then look at the address statistics on the router:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>and then look at the address statistics on the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
========================================================================================================
mobile queue.first 1 balanced 0 0 0 0 0 0 0 0 0
mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+</td></tr></table>
+<p>we see that <em>queue.first</em> appears twice in the list of addresses. The
<code>phs</code>, or phase column shows that there are two phases for the
address. Phase <em>0</em> is for routing message deliveries from producers to
the tail of the queue (the <code>out</code> auto-link associated with the queue).
Phase 1 is for routing deliveries from the head of the queue to
-subscribed consumers.</p></div>
-<div class="paragraph"><p>Note that three deliveries have been counted in the "in" and "out"
+subscribed consumers.</p>
+<p>Note that three deliveries have been counted in the "in" and "out"
columns for phase <em>0</em>. The "in" column represents the three messages
that arrived from <code>simple_send.py</code> and the <code>out</code> column represents the three
-deliveries to the queue on the broker.</p></div>
-<div class="paragraph"><p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p></div>
-<div class="listingblock">
-<div class="content">
+deliveries to the queue on the broker.</p>
+<p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python simple_recv.py -a 127.0.0.1:5672/queue.first -m3
{u'sequence': int32(1)}
{u'sequence': int32(2)}
{u'sequence': int32(3)}</code></pre>
-</div></div>
-<div class="paragraph"><p>We receive the three queued messages. Looking at the addresses again, we
+</td></tr></table>
+<p>We receive the three queued messages. Looking at the addresses again, we
see that phase 1 was used to deliver those messages from the queue to
-the consumer.</p></div>
-<div class="listingblock">
-<div class="content">
+the consumer.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
========================================================================================================
mobile queue.first 1 balanced 0 0 0 0 3 3 0 0 0
mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that even in a multi-router network, and with multiple producers
+</td></tr></table>
+<p>Note that even in a multi-router network, and with multiple producers
and consumers for <em>queue.first</em>, all deliveries will be routed through
-the queue on the connected broker.</p></div>
-</div>
-<div class="sect3">
-<h4 id="sharded-queue-example">2.5.2. Sharded Queue Example</h4>
-<div class="paragraph"><p>Here is an extension of the above example to illustrate how Qpid
+the queue on the connected broker.</p>
+<h4><a name="sharded-queue-example"></a>2.5.2. Sharded Queue Example</h4>
+<p>Here is an extension of the above example to illustrate how Qpid
Dispatch Router can be used to create a distributed queue in which
-multiple brokers share the message-queueing load.</p></div>
-<div class="listingblock">
-<div class="content">
+multiple brokers share the message-queueing load.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker1
role: route-container
@@ -1626,79 +827,66 @@ autoLink {
dir: out
connection: broker2
}</code></pre>
-</div></div>
-<div class="paragraph"><p>In the above configuration, there are two instances of <em>queue.first</em> on
+</td></tr></table>
+<p>In the above configuration, there are two instances of <em>queue.first</em> on
brokers 1 and 2. Message traffic from producers to address <em>queue.first</em>
shall be balanced between the two instance and messages from the queues
shall be balanced across the collection of subscribers to the same
-address.</p></div>
-</div>
-<div class="sect3">
-<h4 id="dynamically-adding-shards">2.5.3. Dynamically Adding Shards</h4>
-<div class="paragraph"><p>Since configurable entities in the router can also be accessed via the
+address.</p>
+<h4><a name="dynamically-adding-shards"></a>2.5.3. Dynamically Adding Shards</h4>
+<p>Since configurable entities in the router can also be accessed via the
management protocol, we can remotely add a shard to the above example
-using <code>qdmanage</code>:</p></div>
-<div class="listingblock">
-<div class="content">
+using <code>qdmanage</code>:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>qdmanage create --type org.apache.qpid.dispatch.connector host=<host> port=<port> name=broker3
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=in connection=broker3
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=out connection=broker3</code></pre>
-</div></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="technical-details-and-specifications">3. Technical Details and Specifications</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="client-compatibility">3.1. Client Compatibility</h3>
-<div class="paragraph"><p>Dispatch Router should, in theory, work with any client that is
-compatible with AMQP 1.0. The following clients have been tested:</p></div>
-<div class="tableblock">
+</td></tr></table>
+<hr>
+<h2><a name="technical-details-and-specifications"></a>3. Technical Details and Specifications</h2>
+<h3><a name="client-compatibility"></a>3.1. Client Compatibility</h3>
+<p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="22%" />
-<col width="78%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Client</em> </th>
-<th align="left" valign="top"><em>Notes</em></th>
+<th align="left" width="22%" valign="top"><em>Client</em> </th>
+<th align="left" width="78%" valign="top"><em>Notes</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">qpid::messaging</p></td>
-<td align="left" valign="top"><p class="table">The Qpid messaging clients work with Dispatch Router
+<td align="left" width="22%" valign="top"><p>qpid::messaging</p></td>
+<td align="left" width="78%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">Proton Reactor</p></td>
-<td align="left" valign="top"><p class="table">The Proton Reactor API is compatible with Dispatch
+<td align="left" width="22%" valign="top"><p>Proton Reactor</p></td>
+<td align="left" width="78%" valign="top"><p>The Proton Reactor API is compatible with Dispatch
Router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">Proton Messenger</p></td>
-<td align="left" valign="top"><p class="table">Messenger works with Dispatch Router.</p></td>
+<td align="left" width="22%" valign="top"><p>Proton Messenger</p></td>
+<td align="left" width="78%" valign="top"><p>Messenger works with Dispatch Router.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-<div class="sect2">
-<h3 id="addressing">3.2. Addressing</h3>
-<div class="paragraph"><p>AMQP addresses are used to control the flow of messages across a network
+<h3><a name="addressing"></a>3.2. Addressing</h3>
+<p>AMQP addresses are used to control the flow of messages across a network
of routers. Addresses are used in a number of different places in the
AMQP 1.0 protocol. They can be used in a specific message in the <code>to</code>
and <code>reply-to</code> fields of a message’s properties. They are also used
during the creation of links in the <code>address</code> field of a <code>source</code> or
-a <code>target</code>.</p></div>
-<div class="paragraph"><p>Addresses designate various kinds of entities in a messaging network:</p></div>
-<div class="ulist"><ul>
+a <code>target</code>.</p>
+<p>Addresses designate various kinds of entities in a messaging network:</p>
+<ul>
<li>
<p>
Endpoint processes that consume data or offer a service
@@ -1713,7 +901,7 @@ Topics that match multiple consumers to multiple producers
<p>
Entities within a messaging broker:
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Queues
@@ -1729,23 +917,23 @@ Durable Topics
Exchanges
</p>
</li>
-</ul></div>
+</ul>
</li>
-</ul></div>
-<div class="paragraph"><p>The syntax of an AMQP address is opaque as far as the router network is
+</ul>
+<p>The syntax of an AMQP address is opaque as far as the router network is
concerned. A syntactical structure may be used by the administrator that
creates addresses, but the router treats them as opaque strings. Routers
consider addresses to be mobile such that any address may be directly
connected to any router in a network and may move around the topology.
In cases where messages are broadcast to or balanced across multiple
consumers, an address may be connected to multiple routers in the
-network.</p></div>
-<div class="paragraph"><p>Addresses have semantics associated with them. When an address is
+network.</p>
+<p>Addresses have semantics associated with them. When an address is
created in the network, it is assigned a set of semantics (and access
rules) during a process called provisioning. The semantics of an address
-control how routers behave when they see the address being used.</p></div>
-<div class="paragraph"><p>Address semantics include the following considerations:</p></div>
-<div class="ulist"><ul>
+control how routers behave when they see the address being used.</p>
+<p>Address semantics include the following considerations:</p>
+<ul>
<li>
<p>
<em>Routing pattern</em> - direct, multicast, balanced
@@ -1761,40 +949,37 @@ control how routers behave when they see the address being used.</p></div>
<em>Reliability</em> - N destinations, etc.
</p>
</li>
-</ul></div>
-<div class="sect3">
-<h4 id="routing-patterns">3.2.1. Routing patterns</h4>
-<div class="paragraph"><p>Routing patterns constrain the paths that a message can take across a
-network.</p></div>
-<div class="tableblock">
+</ul>
+<h4><a name="routing-patterns"></a>3.2.1. Routing patterns</h4>
+<p>Routing patterns constrain the paths that a message can take across a
+network.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="18%" />
-<col width="82%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="18%" valign="top"><em>Pattern</em> </th>
+<th align="left" width="82%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><em>Direct</em></p></td>
-<td align="left" valign="top"><p class="table">Direct routing allows for only one consumer to use an address
+<td align="left" width="18%" valign="top"><p><em>Direct</em></p></td>
+<td align="left" width="82%" valign="top"><p>Direct routing allows for only one consumer to use an address
at a time. Messages (or links) follow the lowest cost path across the
network from the sender to the one receiver.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>Multicast</em></p></td>
-<td align="left" valign="top"><p class="table">Multicast routing allows multiple consumers to use the
+<td align="left" width="18%" valign="top"><p><em>Multicast</em></p></td>
+<td align="left" width="82%" valign="top"><p>Multicast routing allows multiple consumers to use the
same address at the same time. Messages are routed such that each
consumer receives a copy of the message.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>Balanced</em></p></td>
-<td align="left" valign="top"><p class="table">Balanced routing also allows multiple consumers to use the
+<td align="left" width="18%" valign="top"><p><em>Balanced</em></p></td>
+<td align="left" width="82%" valign="top"><p>Balanced routing also allows multiple consumers to use the
same address. In this case, messages are routed to exactly one of the
consumers, and the network attempts to balance the traffic load across
the set of consumers using the same address.</p></td>
@@ -1802,59 +987,53 @@ the set of consumers using the same address.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="routing-mechanisms">3.2.2. Routing mechanisms</h4>
-<div class="paragraph"><p>The fact that addresses can be used in different ways suggests that
+<h4><a name="routing-mechanisms"></a>3.2.2. Routing mechanisms</h4>
+<p>The fact that addresses can be used in different ways suggests that
message routing can be accomplished in different ways. Before going into
the specifics of the different routing mechanisms, it would be good to
-first define what is meant by the term <em>routing</em>:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="paragraph"><p>In a network built of multiple routers connected by connections (i.e.,
+first define what is meant by the term <em>routing</em>:</p>
+<blockquote>
+<p>In a network built of multiple routers connected by connections (i.e.,
nodes and edges in a graph), <em>routing</em> determines which connection to
use to send a message directly to its destination or one step closer to
-its destination.</p></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="paragraph"><p>Each router serves as the terminus of a collection of incoming and
+its destination.</p>
+<p align="right">
+</p>
+</blockquote>
+<p>Each router serves as the terminus of a collection of incoming and
outgoing links. The links either connect directly to endpoints that
produce and consume messages, or they connect to other routers in the
-network along previously established connections.</p></div>
-<div class="sect4">
-<h5 id="message-routing">Message routing</h5>
-<div class="paragraph"><p>Message routing occurs upon delivery of a message and is done based on
-the address in the message’s <code>to</code> field.</p></div>
-<div class="paragraph"><p>When a delivery arrives on an incoming link, the router extracts the
+network along previously established connections.</p>
+<h5><a name="message-routing"></a>Message routing</h5>
+<p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <code>to</code> field.</p>
+<p>When a delivery arrives on an incoming link, the router extracts the
address from the delivered message’s <code>to</code> field and looks the address up
in its routing table. The lookup results in zero or more outgoing links
-onto which the message shall be resent.</p></div>
-<div class="tableblock">
+onto which the message shall be resent.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="20%" />
-<col width="80%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Delivery</em> </th>
-<th align="left" valign="top"><em>Handling</em></th>
+<th align="left" width="20%" valign="top"><em>Delivery</em> </th>
+<th align="left" width="80%" valign="top"><em>Handling</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><em>pre-settled</em></p></td>
-<td align="left" valign="top"><p class="table">If the arriving delivery is pre-settled (i.e., fire and
+<td align="left" width="20%" valign="top"><p><em>pre-settled</em></p></td>
+<td align="left" width="80%" valign="top"><p>If the arriving delivery is pre-settled (i.e., fire and
forget), the incoming delivery shall be settled by the router, and the
outgoing deliveries shall also be pre-settled. In other words, the
pre-settled nature of the message delivery is propagated across the
network to the message’s destination.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>unsettled</em></p></td>
-<td align="left" valign="top"><p class="table">Unsettled delivery is also propagated across the network.
+<td align="left" width="20%" valign="top"><p><em>unsettled</em></p></td>
+<td align="left" width="80%" valign="top"><p>Unsettled delivery is also propagated across the network.
Because unsettled delivery records cannot be discarded, the router
tracks the incoming deliveries and keeps the association of the incoming
deliveries to the resulting outgoing deliveries. This kept association
@@ -1865,95 +1044,83 @@ message traveled.</p></td>
</tbody>
</table>
</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="amqp-mapping">3.3. AMQP Mapping</h3>
-<div class="paragraph"><p>Dispatch Router is an AMQP router and as such, it provides extensions,
+<h3><a name="amqp-mapping"></a>3.3. AMQP Mapping</h3>
+<p>Dispatch Router is an AMQP router and as such, it provides extensions,
code-points, and semantics for routing over AMQP. This page documents the
-details of Dispatch Router’s use of AMQP.</p></div>
-<div class="sect3">
-<h4 id="message-annotations">3.3.1. Message Annotations</h4>
-<div class="paragraph"><p>The following Message Annotation fields are defined by Dispatch Router:</p></div>
-<div class="tableblock">
+details of Dispatch Router’s use of AMQP.</p>
+<h4><a name="message-annotations"></a>3.3.1. Message Annotations</h4>
+<p>The following Message Annotation fields are defined by Dispatch Router:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="19%" />
-<col width="58%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Field</em> </th>
-<th align="left" valign="top"><em>Type</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="23%" valign="top"><em>Field</em> </th>
+<th align="left" width="19%" valign="top"><em>Type</em> </th>
+<th align="left" width="58%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.ingress</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">The identity of the ingress router for a
+<td align="left" width="23%" valign="top"><p>x-opt-qd.ingress</p></td>
+<td align="left" width="19%" valign="top"><p>string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.trace</p></td>
-<td align="left" valign="top"><p class="table">list of string</p></td>
-<td align="left" valign="top"><p class="table">The list of routers through which this
+<td align="left" width="23%" valign="top"><p>x-opt-qd.trace</p></td>
+<td align="left" width="19%" valign="top"><p>list of string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.to</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">To-Override for message-routed messages. If this
+<td align="left" width="23%" valign="top"><p>x-opt-qd.to</p></td>
+<td align="left" width="19%" valign="top"><p>string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.phase</p></td>
-<td align="left" valign="top"><p class="table">integer</p></td>
-<td align="left" valign="top"><p class="table">The address-phase, if not zero, for messages
+<td align="left" width="23%" valign="top"><p>x-opt-qd.phase</p></td>
+<td align="left" width="19%" valign="top"><p>integer</p></td>
+<td align="left" width="58%" valign="top"><p>The address-phase, if not zero, for messages
flowing between routers.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="sourcetarget-capabilities">3.3.2. Source/Target Capabilities</h4>
-<div class="paragraph"><p>The following Capability values are used in Sources and Targets.</p></div>
-<div class="tableblock">
+<h4><a name="sourcetarget-capabilities"></a>3.3.2. Source/Target Capabilities</h4>
+<p>The following Capability values are used in Sources and Targets.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="19%" />
-<col width="81%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Capability</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="19%" valign="top"><em>Capability</em> </th>
+<th align="left" width="81%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">qd.router</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that are
+<td align="left" width="19%" valign="top"><p>qd.router</p></td>
+<td align="left" width="81%" valign="top"><p>This capability is added to sources and targets that are
used for inter-router message exchange. This capability denotes a link
used for router-control messages flowing between routers.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">qd.router-data</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that
+<td align="left" width="19%" valign="top"><p>qd.router-data</p></td>
+<td align="left" width="81%" valign="top"><p>This capability is added to sources and targets that
are used for inter-router message exchange. This capability denotes a
link used for user messages being message-routed across an inter-router
connection.</p></td>
@@ -1961,27 +1128,23 @@ connection.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-node-properties">3.3.3. Dynamic-Node-Properties</h4>
-<div class="paragraph"><p>The following dynamic-node-properties are used by Dispatch in Sources.</p></div>
-<div class="tableblock">
+<h4><a name="dynamic-node-properties"></a>3.3.3. Dynamic-Node-Properties</h4>
+<p>The following dynamic-node-properties are used by Dispatch in Sources.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="77%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Property</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="23%" valign="top"><em>Property</em> </th>
+<th align="left" width="77%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.address</p></td>
-<td align="left" valign="top"><p class="table">The node address describing the destination desired
+<td align="left" width="23%" valign="top"><p>x-opt-qd.address</p></td>
+<td align="left" width="77%" valign="top"><p>The node address describing the destination desired
for a dynamic source. If this is absent, the router will terminate any
dynamic receivers. If this address is present, the router will use the
address to route the dynamic link attach to the proper destination
@@ -1990,48 +1153,43 @@ container.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="addresses-and-address-formats">3.3.4. Addresses and Address Formats</h4>
-<div class="paragraph"><p>The following AMQP addresses and address patterns are used within
-Dispatch Router.</p></div>
-<div class="sect4">
-<h5 id="address-patterns">Address Patterns</h5>
-<div class="tableblock">
+<h4><a name="addresses-and-address-formats"></a>3.3.4. Addresses and Address Formats</h4>
+<p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p>
+<h5><a name="address-patterns"></a>Address Patterns</h5>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="38%" />
-<col width="62%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="38%" valign="top"><em>Pattern</em> </th>
+<th align="left" width="62%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">An address that references a locally attached endpoint.
+<td align="left" width="38%" valign="top"><p><code>_local/<addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>An address that references a locally attached endpoint.
Messages using this address pattern shall not be routed over more than
one link.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/<router>/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">An address that references an endpoint attached to a specific router
+<td align="left" width="38%" valign="top"><p><code>_topo/0/<router>/<addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>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.</p>
-<p class="table">The <em>0</em> component immediately preceding the router-id is a placeholder
+<p>The <em>0</em> component immediately preceding the router-id is a placeholder
for an <em>area</em> which may be used in the future if area routing is
implemented.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code><addr></code></p></td>
-<td align="left" valign="top"><p class="table">A mobile address. An address of this format represents an
+<td align="left" width="38%" valign="top"><p><code><addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>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
@@ -2040,66 +1198,59 @@ addresses.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect4">
-<h5 id="supported-addresses">Supported Addresses</h5>
-<div class="tableblock">
+<h5><a name="supported-addresses"></a>Supported Addresses</h5>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="36%" />
-<col width="64%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Address</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="36%" valign="top"><em>Address</em> </th>
+<th align="left" width="64%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><code>$management</code></p></td>
-<td align="left" valign="top"><p class="table">The management agent on the attached router/container.
+<td align="left" width="36%" valign="top"><p><code>$management</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/$management</code></p></td>
-<td align="left" valign="top"><p class="table">The management agent at Router.E in area
+<td align="left" width="36%" valign="top"><p><code>_topo/0/Router.E/$management</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdhello</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+<td align="left" width="36%" valign="top"><p><code>_local/qdhello</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+<td align="left" width="36%" valign="top"><p><code>_local/qdrouter</code></p></td>
+<td align="left" width="64%" valign="top"><p>The router entity in each of the connected routers.
This address is used by a router to communicate with other routers in
the network.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity at the specifically
+<td align="left" width="36%" valign="top"><p><code>_topo/0/Router.E/qdrouter</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</h4>
-<div class="paragraph"><p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
-emerging AMQP Management specification (draft 9).</p></div>
-<div class="paragraph"><p>Differences from the specification:</p></div>
-<div class="ulist"><ul>
+<h4><a name="implementation-of-the-amqp-management-specification"></a>3.3.5. Implementation of the AMQP Management Specification</h4>
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p>
+<p>Differences from the specification:</p>
+<ul>
<li>
<p>
The <code>name</code> attribute is not required when an entity is created. If
@@ -2116,14 +1267,14 @@ The <code>REGISTER</code> and <code>DEREGISTER</code> operations are not impleme
= Management Schema
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>This chapter documents the set of <strong>management entity types</strong> that define
+</ul>
+<p>This chapter documents the set of <strong>management entity types</strong> that define
configuration and management of a Dispatch Router. A management entity type has
a set of <strong>attributes</strong> that can be read, some attributes can also be
-updated. Some entity types also support <strong>operations</strong> that can be called.</p></div>
-<div class="paragraph"><p>All management entity types have the following standard attributes:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+updated. Some entity types also support <strong>operations</strong> that can be called.</p>
+<p>All management entity types have the following standard attributes:</p>
+<dl>
+<dt>
type
</dt>
<dd>
@@ -2134,7 +1285,7 @@ type
tools will accept the short or long name.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
name
</dt>
<dd>
@@ -2143,7 +1294,7 @@ name
that need to refer to the named entity.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
identity
</dt>
<dd>
@@ -2153,10 +1304,10 @@ identity
<code>listener/localhost:amqp</code>
</p>
</dd>
-</dl></div>
-<div class="paragraph
<TRUNCATED>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/book.pdf
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/book.pdf b/content/releases/qpid-dispatch-master/book.pdf
index dbd7f6e..4896e01 100755
Binary files a/content/releases/qpid-dispatch-master/book.pdf and b/content/releases/qpid-dispatch-master/book.pdf differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[02/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html.in b/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html.in
index 75de632..08aeede 100644
--- a/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html.in
+++ b/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html.in
@@ -1,788 +1,38 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd.conf(5)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd.conf(5) Manual Page
-</h1>
<h2>NAME</h2>
-<div class="sectionbody">
<p>qdrouterd.conf -
configuration file for the dispatch router.
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Provides the initial configuration when <em>qdrouterd(8)</em> starts. The configuration
-of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The configuration file is made up of sections with this syntax:</p></div>
-<div class="listingblock">
-<div class="content">
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p>Provides the initial configuration when <b>qdrouterd(8)</b> starts. The configuration
+of a running router can be modified using <b>qdmanage(8)</b>.</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>The configuration file is made up of sections with this syntax:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>sectionName {
attributeName: attributeValue
attributeName: attributeValue
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>For example you can define a router using the <em>router</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>For example you can define a router using the <b>router</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>router {
mode: standalone
id: Router.A
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a listener using the <em>listener</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>or define a listener using the <b>listener</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>listener {
host: 0.0.0.0
port: 20102
saslMechanisms: ANONYMOUS
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a connector using the <em>connector</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>or define a connector using the <b>connector</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
role: inter-router
host: 0.0.0.0
@@ -790,12 +40,11 @@ of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
saslMechanisms: ANONYMOUS
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>An <em>sslProfile</em> section with SSL credentials can be included in multiple <em>listener</em> or <em>connector</em> entities. Here’s an example, note
-how the <em>sslProfile</em> attribute of <em>listener</em> sections references the <em>name</em>
-attribute of <em>sslProfile</em> sections.</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>An <b>sslProfile</b> section with SSL credentials can be included in multiple <b>listener</b> or <b>connector</b> entities. Here’s an example, note
+how the <b>sslProfile</b> attribute of <b>listener</b> sections references the <b>name</b>
+attribute of <b>sslProfile</b> sections.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>sslProfile {
name: my-ssl
certDb: ca-certificate-1.pem
@@ -809,998 +58,949 @@ listener {
port: 20102
saslMechanisms: ANONYMOUS
}</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_configuration_sections">Configuration Sections</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_sslprofile">sslProfile</h3>
-<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
-<div class="paragraph"><p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>certDb</em> (path)
+</td></tr></table>
+<h2><a name="_configuration_sections"></a>Configuration Sections</h2>
+<h3><a name="_sslprofile"></a>sslProfile</h3>
+<p>Attributes for setting TLS/SSL configuration for connections.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>certFile</em> (path)
+<dt>
+<b>certDb</b> (path)
</dt>
<dd>
<p>
- The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
+ The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
</p>
</dd>
-<dt class="hdlist1">
-<em>keyFile</em> (path)
+<dt>
+<b>certFile</b> (path)
</dt>
<dd>
<p>
- The absolute path to the file containing the PEM-formatted private key for the above certificate.
+ The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
</p>
</dd>
-<dt class="hdlist1">
-<em>passwordFile</em> (path)
+<dt>
+<b>keyFile</b> (path)
</dt>
<dd>
<p>
- If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
+ The absolute path to the file containing the PEM-formatted private key for the above certificate.
</p>
</dd>
-<dt class="hdlist1">
-<em>password</em> (string)
+<dt>
+<b>passwordFile</b> (path)
</dt>
<dd>
<p>
- An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
+ If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
</p>
</dd>
-<dt class="hdlist1">
-<em>uidFormat</em> (string)
+<dt>
+<b>password</b> (string)
</dt>
<dd>
<p>
- A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
+ An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <b>password</b> option. Don’t use both password and passwordFile in the same profile.
</p>
</dd>
-<dt class="hdlist1">
-<em>displayNameFile</em> (string)
+<dt>
+<b>uidFormat</b> (string)
</dt>
<dd>
<p>
- The absolute path to the file containing the unique id to dispay name mapping
+ A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <b>cou</b> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <b>o2</b> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <b>c</b>( ISO3166 two character country code), <b>s</b>(state or province), <b>l</b>(Locality; generally - city), <b>o</b>(Organization - Company Name), <b>u</b>(Organization Unit - typically certificate type or brand), <b>n</b>(CommonName - typically a user name for client certificates) and <b>1</b>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and 2 (sha256 certifi
cate fingerprint) and 5 (sha512 certificate fingerprint).
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string)
+<dt>
+<b>displayNameFile</b> (string)
</dt>
<dd>
<p>
- name of the sslProfile
+ The absolute path to the file containing the unique id to dispay name mapping
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_container">container</h3>
-<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>containerName</em> (string)
+</dl>
+<h3><a name="_container"></a>container</h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<dl>
+<dt>
+<b>containerName</b> (string)
</dt>
<dd>
<p>
The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
</p>
</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
+<dt>
+<b>workerThreads</b> (integer, default=4)
</dt>
<dd>
<p>
The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
</p>
</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
+<dt>
+<b>debugDump</b> (path)
</dt>
<dd>
<p>
A file to dump debugging information that can’t be logged normally.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
+<dt>
+<b>saslConfigPath</b> (path)
</dt>
<dd>
<p>
Absolute path to the SASL configuration file.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string)
+<dt>
+<b>saslConfigName</b> (string)
</dt>
<dd>
<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+ Name of the SASL configuration. This string + <b>.conf</b> is the name of the configuration file.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_router">router</h3>
-<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>routerId</em> (string)
+</dl>
+<h3><a name="_router"></a>router</h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<dl>
+<dt>
+<b>routerId</b> (string)
</dt>
<dd>
<p>
(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
</p>
</dd>
-<dt class="hdlist1">
-<em>id</em> (string)
+<dt>
+<b>id</b> (string)
</dt>
<dd>
<p>
Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
</p>
</dd>
-<dt class="hdlist1">
-<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>)
+<dt>
+<b>mode</b> (One of [<b>standalone</b>, <b>interior</b>], default=<b>standalone</b>)
</dt>
<dd>
<p>
In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
</p>
</dd>
-<dt class="hdlist1">
-<em>helloInterval</em> (integer, default=1)
+<dt>
+<b>helloInterval</b> (integer, default=1)
</dt>
<dd>
<p>
Interval in seconds between HELLO messages sent to neighbor routers.
</p>
</dd>
-<dt class="hdlist1">
-<em>helloMaxAge</em> (integer, default=3)
+<dt>
+<b>helloMaxAge</b> (integer, default=3)
</dt>
<dd>
<p>
Time in seconds after which a neighbor is declared lost if no HELLO is received.
</p>
</dd>
-<dt class="hdlist1">
-<em>raInterval</em> (integer, default=30)
+<dt>
+<b>raInterval</b> (integer, default=30)
</dt>
<dd>
<p>
Interval in seconds between Router-Advertisements sent to all routers in a stable network.
</p>
</dd>
-<dt class="hdlist1">
-<em>raIntervalFlux</em> (integer, default=4)
+<dt>
+<b>raIntervalFlux</b> (integer, default=4)
</dt>
<dd>
<p>
Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
</p>
</dd>
-<dt class="hdlist1">
-<em>remoteLsMaxAge</em> (integer, default=60)
+<dt>
+<b>remoteLsMaxAge</b> (integer, default=60)
</dt>
<dd>
<p>
Time in seconds after which link state is declared stale if no RA is received.
</p>
</dd>
-<dt class="hdlist1">
-<em>mobileAddrMaxAge</em> (integer, default=60)
+<dt>
+<b>mobileAddrMaxAge</b> (integer, default=60)
</dt>
<dd>
<p>
(DEPRECATED) This value is no longer used in the router.
</p>
</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
+<dt>
+<b>workerThreads</b> (integer, default=4)
</dt>
<dd>
<p>
The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
</p>
</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
+<dt>
+<b>debugDump</b> (path)
</dt>
<dd>
<p>
A file to dump debugging information that can’t be logged normally.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
+<dt>
+<b>saslConfigPath</b> (path)
</dt>
<dd>
<p>
Absolute path to the SASL configuration file.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string, default=<em>qdrouterd</em>)
+<dt>
+<b>saslConfigName</b> (string, default=<b>qdrouterd</b>)
</dt>
<dd>
<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+ Name of the SASL configuration. This string + <b>.conf</b> is the name of the configuration file.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_listener">listener</h3>
-<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
+</dl>
+<h3><a name="_listener"></a>listener</h3>
+<p>Listens for incoming connections to the router.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- Space separated list of accepted SASL authentication mechanisms.
+ Unique name optionally assigned by user. Can be changed.
</p>
</dd>
-<dt class="hdlist1">
-<em>authenticatePeer</em> (boolean)
+<dt>
+<b>host</b> (string)
</dt>
<dd>
<p>
- yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
+ IP address: ipv4 or ipv6 literal or a host name
</p>
</dd>
-<dt class="hdlist1">
-<em>requireEncryption</em> (boolean)
+<dt>
+<b>port</b> (string)
</dt>
<dd>
<p>
- yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
+ Port number or symbolic service name.
</p>
</dd>
-<dt class="hdlist1">
-<em>requireSsl</em> (boolean)
+<dt>
+<b>protocolFamily</b> (One of [<b>IPv4</b>, <b>IPv6</b>])
</dt>
<dd>
<p>
- yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
+ [<b>IPv4</b>, <b>IPv6</b>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
</p>
</dd>
-<dt class="hdlist1">
-<em>trustedCerts</em> (path)
+<dt>
+<b>role</b> (One of [<b>normal</b>, <b>inter-router</b>, <b>route-container</b>, <b>on-demand</b>])
</dt>
<dd>
<p>
- This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=16384)
+<dt>
+<b>cost</b> (integer)
</dt>
<dd>
<p>
- Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+ For the <b>inter-router</b> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
</p>
</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
+<dt>
+<b>sslProfile</b> (string)
</dt>
<dd>
<p>
- The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>requirePeerAuth</em> (boolean)
+<dt>
+<b>saslMechanisms</b> (string)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+ Space separated list of accepted SASL authentication mechanisms.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowUnsecured</em> (boolean)
+<dt>
+<b>authenticatePeer</b> (boolean)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
+ yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowNoSasl</em> (boolean)
+<dt>
+<b>requireEncryption</b> (boolean)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+ yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
</p>
</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+<dt>
+<b>requireSsl</b> (boolean)
</dt>
<dd>
<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+ yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
</p>
</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
+<dt>
+<b>trustedCerts</b> (path)
</dt>
<dd>
<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+ This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
+<dt>
+<b>maxFrameSize</b> (integer, default=16384)
</dt>
<dd>
<p>
- Unique name optionally assigned by user. Can be changed.
+ Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
</p>
</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
+<dt>
+<b>idleTimeoutSeconds</b> (integer, default=16)
</dt>
<dd>
<p>
- IP address: ipv4 or ipv6 literal or a host name
+ The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
</p>
</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
+<dt>
+<b>requirePeerAuth</b> (boolean)
</dt>
<dd>
<p>
- Port number or symbolic service name.
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+<dt>
+<b>allowUnsecured</b> (boolean)
</dt>
<dd>
<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+ (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
+<dt>
+<b>allowNoSasl</b> (boolean)
</dt>
<dd>
<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
+<dt>
+<b>stripAnnotations</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+ [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
</p>
</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
+<dt>
+<b>linkCapacity</b> (integer)
</dt>
<dd>
<p>
- name of the sslProfile
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_connector">connector</h3>
-<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
+</dl>
+<h3><a name="_connector"></a>connector</h3>
+<p>Establishes an outgoing connection from the router.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- Space separated list of accepted SASL authentication mechanisms.
+ Unique name optionally assigned by user. Can be changed.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowRedirect</em> (boolean, default=True)
+<dt>
+<b>host</b> (string)
</dt>
<dd>
<p>
- Allow the peer to redirect this connection to another address.
+ IP address: ipv4 or ipv6 literal or a host name
</p>
</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=65536)
+<dt>
+<b>port</b> (string)
</dt>
<dd>
<p>
- Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+ Port number or symbolic service name.
</p>
</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
+<dt>
+<b>protocolFamily</b> (One of [<b>IPv4</b>, <b>IPv6</b>])
</dt>
<dd>
<p>
- The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
+ [<b>IPv4</b>, <b>IPv6</b>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
</p>
</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+<dt>
+<b>role</b> (One of [<b>normal</b>, <b>inter-router</b>, <b>route-container</b>, <b>on-demand</b>])
</dt>
<dd>
<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
</p>
</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
+<dt>
+<b>cost</b> (integer)
</dt>
<dd>
<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+ For the <b>inter-router</b> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
</p>
</dd>
-<dt class="hdlist1">
-<em>verifyHostName</em> (boolean, default=True)
+<dt>
+<b>sslProfile</b> (string)
</dt>
<dd>
<p>
- yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>saslUsername</em> (string)
+<dt>
+<b>saslMechanisms</b> (string)
</dt>
<dd>
<p>
- The user name that the connector is using to connect to a peer.
+ Space separated list of accepted SASL authentication mechanisms.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslPassword</em> (string)
+<dt>
+<b>allowRedirect</b> (boolean, default=True)
</dt>
<dd>
<p>
- The password that the connector is using to connect to a peer.
+ Allow the peer to redirect this connection to another address.
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
+<dt>
+<b>maxFrameSize</b> (integer, default=65536)
</dt>
<dd>
<p>
- Unique name optionally assigned by user. Can be changed.
+ Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
</p>
</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
+<dt>
+<b>idleTimeoutSeconds</b> (integer, default=16)
</dt>
<dd>
<p>
- IP address: ipv4 or ipv6 literal or a host name
+ The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
</p>
</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
+<dt>
+<b>stripAnnotations</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- Port number or symbolic service name.
+ [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
</p>
</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+<dt>
+<b>linkCapacity</b> (integer)
</dt>
<dd>
<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
</p>
</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
+<dt>
+<b>verifyHostName</b> (boolean, default=True)
</dt>
<dd>
<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+ yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
</p>
</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
+<dt>
+<b>saslUsername</b> (string)
</dt>
<dd>
<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+ The user name that the connector is using to connect to a peer.
</p>
</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
+<dt>
+<b>saslPassword</b> (string)
</dt>
<dd>
<p>
- name of the sslProfile
+ The password that the connector is using to connect to a peer.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_log">log</h3>
-<div class="paragraph"><p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>module</em> (One of [<em>ROUTER</em>, <em>ROUTER_CORE</em>, <em>ROUTER_HELLO</em>, <em>ROUTER_LS</em>, <em>ROUTER_MA</em>, <em>MESSAGE</em>, <em>SERVER</em>, <em>AGENT</em>, <em>CONTAINER</em>, <em>ERROR</em>, <em>POLICY</em>, <em>DEFAULT</em>], required)
+</dl>
+<h3><a name="_log"></a>log</h3>
+<p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p>
+<dl>
+<dt>
+<b>module</b> (One of [<b>ROUTER</b>, <b>ROUTER_CORE</b>, <b>ROUTER_HELLO</b>, <b>ROUTER_LS</b>, <b>ROUTER_MA</b>, <b>MESSAGE</b>, <b>SERVER</b>, <b>AGENT</b>, <b>CONTAINER</b>, <b>ERROR</b>, <b>POLICY</b>, <b>DEFAULT</b>], required)
</dt>
<dd>
<p>
- Module to configure. The special module <em>DEFAULT</em> specifies defaults for all modules.
+ Module to configure. The special module <b>DEFAULT</b> specifies defaults for all modules.
</p>
</dd>
-<dt class="hdlist1">
-<em>enable</em> (string, default=<em>default</em>, required)
+<dt>
+<b>enable</b> (string)
</dt>
<dd>
<p>
- Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <em>+</em> to enable that level and above. For example <em>trace,debug,warning+</em> means enable trace, debug, warning, error and critical. The value <em>none</em> means disable logging for the module. The value <em>default</em> means use the value from the DEFAULT module.
+ Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <b>+</b> to enable that level and above. For example <b>trace,debug,warning+</b> means enable trace, debug, warning, error and critical. The value <b>none</b> means disable logging for the module.
</p>
</dd>
-<dt class="hdlist1">
-<em>timestamp</em> (boolean)
+<dt>
+<b>timestamp</b> (boolean)
</dt>
<dd>
<p>
Include timestamp in log messages.
</p>
</dd>
-<dt class="hdlist1">
-<em>source</em> (boolean)
+<dt>
+<b>source</b> (boolean)
</dt>
<dd>
<p>
Include source file and line number in log messages.
</p>
</dd>
-<dt class="hdlist1">
-<em>output</em> (string)
+<dt>
+<b>output</b> (string)
</dt>
<dd>
<p>
- Where to send log messages. Can be <em>stderr</em>, <em>syslog</em> or a file name.
+ Where to send log messages. Can be <b>stderr</b>, <b>stdout</b>, <b>syslog</b> or a file name.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_fixedaddress">fixedAddress</h3>
-<div class="paragraph"><p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_fixedaddress"></a>fixedAddress</h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
- The address prefix (always starting with <em>/</em>).
+ The address prefix (always starting with <b>/</b>).
</p>
</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
+<dt>
+<b>phase</b> (integer)
</dt>
<dd>
<p>
The phase of a multi-hop address passing through one or more waypoints.
</p>
</dd>
-<dt class="hdlist1">
-<em>fanout</em> (One of [<em>multiple</em>, <em>single</em>], default=<em>multiple</em>)
+<dt>
+<b>fanout</b> (One of [<b>multiple</b>, <b>single</b>], default=<b>multiple</b>)
</dt>
<dd>
<p>
- One of <em>multiple</em> or <em>single</em>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
+ One of <b>multiple</b> or <b>single</b>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
</p>
</dd>
-<dt class="hdlist1">
-<em>bias</em> (One of [<em>closest</em>, <em>spread</em>], default=<em>closest</em>)
+<dt>
+<b>bias</b> (One of [<b>closest</b>, <b>spread</b>], default=<b>closest</b>)
</dt>
<dd>
<p>
- Only if fanout is single. One of <em>closest</em> or <em>spread</em>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
+ Only if fanout is single. One of <b>closest</b> or <b>spread</b>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_waypoint">waypoint</h3>
-<div class="paragraph"><p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>address</em> (string, required)
+</dl>
+<h3><a name="_waypoint"></a>waypoint</h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<dl>
+<dt>
+<b>address</b> (string, required)
</dt>
<dd>
<p>
The AMQP address of the waypoint.
</p>
</dd>
-<dt class="hdlist1">
-<em>connector</em> (string, required)
+<dt>
+<b>connector</b> (string, required)
</dt>
<dd>
<p>
The name of the on-demand connector used to reach the waypoint’s container.
</p>
</dd>
-<dt class="hdlist1">
-<em>inPhase</em> (integer, default=-1)
+<dt>
+<b>inPhase</b> (integer, default=-1)
</dt>
<dd>
<p>
- The phase of the address as it is routed <em>to</em> the waypoint.
+ The phase of the address as it is routed <b>to</b> the waypoint.
</p>
</dd>
-<dt class="hdlist1">
-<em>outPhase</em> (integer, default=-1)
+<dt>
+<b>outPhase</b> (integer, default=-1)
</dt>
<dd>
<p>
- The phase of the address as it is routed <em>from</em> the waypoint.
+ The phase of the address as it is routed <b>from</b> the waypoint.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroutepattern">linkRoutePattern</h3>
-<div class="paragraph"><p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_linkroutepattern"></a>linkRoutePattern</h3>
+<p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
- An address prefix to match against target and source addresses. This pattern must be of the form <em><text>.<text1>.<textN></em> or <em><text></em> or <em><text>.</em> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <em>org.apache</em> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
+ An address prefix to match against target and source addresses. This pattern must be of the form <b><text>.<text1>.<textN></b> or <b><text></b> or <b><text>.</b> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <b>org.apache</b> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>], default=<em>both</em>)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- Link direction for match: <em>in</em> matches only links inbound to the client; <em>out</em> matches only links outbound from the client; <em>both</em> matches any link.
+ Link direction for match: <b>in</b> matches only links inbound to the client; <b>out</b> matches only links outbound from the client; <b>both</b> matches any link.
</p>
</dd>
-<dt class="hdlist1">
-<em>connector</em> (string)
+<dt>
+<b>connector</b> (string)
</dt>
<dd>
<p>
The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_address">address</h3>
-<div class="paragraph"><p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_address"></a>address</h3>
+<p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
The address prefix for the configured settings
</p>
</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>multicast</em>, <em>closest</em>, <em>balanced</em>], default=<em>balanced</em>)
+<dt>
+<b>distribution</b> (One of [<b>multicast</b>, <b>closest</b>, <b>balanced</b>], default=<b>balanced</b>)
</dt>
<dd>
<p>
Treatment of traffic associated with the address
</p>
</dd>
-<dt class="hdlist1">
-<em>waypoint</em> (boolean)
+<dt>
+<b>waypoint</b> (boolean)
</dt>
<dd>
<p>
Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressPhase</em> (integer)
+<dt>
+<b>ingressPhase</b> (integer)
</dt>
<dd>
<p>
Advanced - Override the ingress phase for this address
</p>
</dd>
-<dt class="hdlist1">
-<em>egressPhase</em> (integer)
+<dt>
+<b>egressPhase</b> (integer)
</dt>
<dd>
<p>
Advanced - Override the egress phase for this address
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroute">linkRoute</h3>
-<div class="paragraph"><p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_linkroute"></a>linkRoute</h3>
+<p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
The address prefix for the configured settings
</p>
</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
+<dt>
+<b>containerId</b> (string)
</dt>
<dd>
<p>
ContainerID for the target container
</p>
</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
+<dt>
+<b>connection</b> (string)
</dt>
<dd>
<p>
The name from a connector or listener
</p>
</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>linkBalanced</em>], default=<em>linkBalanced</em>)
+<dt>
+<b>distribution</b> (One of [<b>linkBalanced</b>], default=<b>linkBalanced</b>)
</dt>
<dd>
<p>
Treatment of traffic associated with the address
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>], required)
</dt>
<dd>
<p>
- The permitted direction of links: <em>in</em> means client senders; <em>out</em> means client receivers
+ The permitted direction of links: <b>in</b> means client senders; <b>out</b> means client receivers
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_autolink">autoLink</h3>
-<div class="paragraph"><p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>addr</em> (string, required)
+</dl>
+<h3><a name="_autolink"></a>autoLink</h3>
+<p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p>
+<dl>
+<dt>
+<b>addr</b> (string, required)
</dt>
<dd>
<p>
The address of the provisioned object
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>], required)
</dt>
<dd>
<p>
The direction of the link to be created. In means into the router, out means out of the router.
</p>
</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
+<dt>
+<b>phase</b> (integer)
</dt>
<dd>
<p>
- The address phase for this link. Defaults to <em>0</em> for <em>out</em> links and <em>1</em> for <em>in</em> links.
+ The address phase for this link. Defaults to <b>0</b> for <b>out</b> links and <b>1</b> for <b>in</b> links.
</p>
</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
+<dt>
+<b>containerId</b> (string)
</dt>
<dd>
<p>
ContainerID for the target container
</p>
</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
+<dt>
+<b>connection</b> (string)
</dt>
<dd>
<p>
The name from a connector or listener
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_console">console</h3>
-<div class="paragraph"><p>Start a websocket/tcp proxy and http file server to serve the web console</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>listener</em> (string)
+</dl>
+<h3><a name="_console"></a>console</h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+<dl>
+<dt>
+<b>listener</b> (string)
</dt>
<dd>
<p>
The name of the listener to send the proxied tcp traffic to.
</p>
</dd>
-<dt class="hdlist1">
-<em>wsport</em> (integer, default=5673)
+<dt>
+<b>wsport</b> (integer, default=5673)
</dt>
<dd>
<p>
port on which to listen for websocket traffic
</p>
</dd>
-<dt class="hdlist1">
-<em>proxy</em> (string)
+<dt>
+<b>proxy</b> (string)
</dt>
<dd>
<p>
The full path to the proxy program to run.
</p>
</dd>
-<dt class="hdlist1">
-<em>home</em> (string)
+<dt>
+<b>home</b> (string)
</dt>
<dd>
<p>
The full path to the html/css/js files for the console.
</p>
</dd>
-<dt class="hdlist1">
-<em>args</em> (string)
+<dt>
+<b>args</b> (string)
</dt>
<dd>
<p>
Optional args to pass the proxy program for logging, authentication, etc.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policy">policy</h3>
-<div class="paragraph"><p>Defines global connection limit</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maximumConnections</em> (integer)
+</dl>
+<h3><a name="_policy"></a>policy</h3>
+<p>Defines global connection limit</p>
+<dl>
+<dt>
+<b>maximumConnections</b> (integer)
</dt>
<dd>
<p>
Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.
</p>
</dd>
-<dt class="hdlist1">
-<em>enableAccessRules</em> (boolean)
+<dt>
+<b>enableAccessRules</b> (boolean)
</dt>
<dd>
<p>
Enable user rule set processing and connection denial.
</p>
</dd>
-<dt class="hdlist1">
-<em>policyFolder</em> (path)
+<dt>
+<b>policyFolder</b> (path)
</dt>
<dd>
<p>
The absolute path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.
</p>
</dd>
-<dt class="hdlist1">
-<em>defaultApplication</em> (string)
+<dt>
+<b>defaultApplication</b> (string)
</dt>
<dd>
<p>
Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.
</p>
</dd>
-<dt class="hdlist1">
-<em>defaultApplicationEnabled</em> (boolean)
+<dt>
+<b>defaultApplicationEnabled</b> (boolean)
</dt>
<dd>
<p>
Enable defaultApplication policy fallback logic.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policyruleset">policyRuleset</h3>
-<div class="paragraph"><p>Per application definition of the locations from which users may connect and the groups to which users belong.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maxConnections</em> (integer)
+</dl>
+<h3><a name="_policyruleset"></a>policyRuleset</h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<dl>
+<dt>
+<b>maxConnections</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxConnPerUser</em> (integer)
+<dt>
+<b>maxConnPerUser</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxConnPerHost</em> (integer)
+<dt>
+<b>maxConnPerHost</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>userGroups</em> (map)
+<dt>
+<b>userGroups</b> (map)
</dt>
<dd>
<p>
- A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed <em>restricted</em>. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.
+ A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed <b>restricted</b>. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressHostGroups</em> (map)
+<dt>
+<b>ingressHostGroups</b> (map)
</dt>
<dd>
<p>
- A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address <em>*</em> represents any host address.
+ A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address <b>*</b> represents any host address.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressPolicies</em> (map)
+<dt>
+<b>ingressPolicies</b> (map)
</dt>
<dd>
<p>
A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.
</p>
</dd>
-<dt class="hdlist1">
-<em>connectionAllowDefault</em> (boolean)
+<dt>
+<b>connectionAllowDefault</b> (boolean)
</dt>
<dd>
<p>
- Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <em>default</em> user group and receive <em>default</em> settings.
+ Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <b>default</b> user group and receive <b>default</b> settings.
</p>
</dd>
-<dt class="hdlist1">
-<em>settings</em> (map)
+<dt>
+<b>settings</b> (map)
</dt>
<dd>
<p>
A map where each key is a user group name and the value is a map of the corresponding settings for that group.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:42:34 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[03/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdrouterd.8.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdrouterd.8.html.in b/input/releases/qpid-dispatch-master/qdrouterd.8.html.in
index d0449f3..23bb412 100644
--- a/input/releases/qpid-dispatch-master/qdrouterd.8.html.in
+++ b/input/releases/qpid-dispatch-master/qdrouterd.8.html.in
@@ -1,783 +1,29 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd(8) Manual Page
-</h1>
<h2>NAME</h2>
-<div class="sectionbody">
<p>qdrouterd -
routes AMQP messages.
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdrouterd</strong> [<b>OPTIONS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
AMQP 1.0 messages between endpoints, such as messaging clients and
-servers.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
-: Load configuration from file at PATH</p></div>
-<div class="paragraph"><p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
-: Location of Dispatch’s Python library</p></div>
-<div class="paragraph"><p>-d, --daemon
-: Run process as a SysV-style daemon</p></div>
-<div class="paragraph"><p>-P, --pidfile
-: If daemon, the file for the stored daemon pid</p></div>
-<div class="paragraph"><p>-U, --user
-: If daemon, the username to run as</p></div>
-<div class="paragraph"><p>-h, --help
-: Print this help</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
+servers.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p>
+<p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p>
+<p>-d, --daemon
+: Run process as a SysV-style daemon</p>
+<p>-P, --pidfile
+: If daemon, the file for the stored daemon pid</p>
+<p>-U, --user
+: If daemon, the username to run as</p>
+<p>-h, --help
+: Print this help</p>
+<h2><a name="_files"></a>FILES</h2>
+<dl>
+<dt>
/usr/local/etc/qdrouterd.conf
</dt>
<dd>
@@ -785,22 +31,7 @@ servers.</p></div>
Configuration flie.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd.conf(5)</b>, <b>qdstat(8)</b>, <b>qdmanage(8)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html b/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html
deleted file mode 100644
index 75de632..0000000
--- a/input/releases/qpid-dispatch-master/qdrouterd.conf.5.html
+++ /dev/null
@@ -1,1806 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd.conf(5)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd.conf(5) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
-<p>qdrouterd.conf -
- configuration file for the dispatch router.
-</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Provides the initial configuration when <em>qdrouterd(8)</em> starts. The configuration
-of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The configuration file is made up of sections with this syntax:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>sectionName {
- attributeName: attributeValue
- attributeName: attributeValue
- ...
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>For example you can define a router using the <em>router</em> section</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>router {
- mode: standalone
- id: Router.A
- ...
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a listener using the <em>listener</em> section</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>listener {
- host: 0.0.0.0
- port: 20102
- saslMechanisms: ANONYMOUS
- ...
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a connector using the <em>connector</em> section</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>connector {
- role: inter-router
- host: 0.0.0.0
- port: 20003
- saslMechanisms: ANONYMOUS
- ...
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>An <em>sslProfile</em> section with SSL credentials can be included in multiple <em>listener</em> or <em>connector</em> entities. Here’s an example, note
-how the <em>sslProfile</em> attribute of <em>listener</em> sections references the <em>name</em>
-attribute of <em>sslProfile</em> sections.</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>sslProfile {
- name: my-ssl
- certDb: ca-certificate-1.pem
- certFile: server-certificate-1.pem
- keyFile: server-private-key.pem
-}
-
-listener {
- sslProfile: my-ssl
- host: 0.0.0.0
- port: 20102
- saslMechanisms: ANONYMOUS
-}</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_configuration_sections">Configuration Sections</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_sslprofile">sslProfile</h3>
-<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
-<div class="paragraph"><p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>certDb</em> (path)
-</dt>
-<dd>
-<p>
- The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
-</p>
-</dd>
-<dt class="hdlist1">
-<em>certFile</em> (path)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>keyFile</em> (path)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the PEM-formatted private key for the above certificate.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>passwordFile</em> (path)
-</dt>
-<dd>
-<p>
- If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>password</em> (string)
-</dt>
-<dd>
-<p>
- An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>uidFormat</em> (string)
-</dt>
-<dd>
-<p>
- A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
-</p>
-</dd>
-<dt class="hdlist1">
-<em>displayNameFile</em> (string)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the unique id to dispay name mapping
-</p>
-</dd>
-<dt class="hdlist1">
-<em>name</em> (string)
-</dt>
-<dd>
-<p>
- name of the sslProfile
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_container">container</h3>
-<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>containerName</em> (string)
-</dt>
-<dd>
-<p>
- The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
-</dt>
-<dd>
-<p>
- The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
-</p>
-</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
-</dt>
-<dd>
-<p>
- A file to dump debugging information that can’t be logged normally.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
-</dt>
-<dd>
-<p>
- Absolute path to the SASL configuration file.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string)
-</dt>
-<dd>
-<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_router">router</h3>
-<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>routerId</em> (string)
-</dt>
-<dd>
-<p>
- (DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
-</p>
-</dd>
-<dt class="hdlist1">
-<em>id</em> (string)
-</dt>
-<dd>
-<p>
- Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
-</p>
-</dd>
-<dt class="hdlist1">
-<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>)
-</dt>
-<dd>
-<p>
- In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>helloInterval</em> (integer, default=1)
-</dt>
-<dd>
-<p>
- Interval in seconds between HELLO messages sent to neighbor routers.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>helloMaxAge</em> (integer, default=3)
-</dt>
-<dd>
-<p>
- Time in seconds after which a neighbor is declared lost if no HELLO is received.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>raInterval</em> (integer, default=30)
-</dt>
-<dd>
-<p>
- Interval in seconds between Router-Advertisements sent to all routers in a stable network.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>raIntervalFlux</em> (integer, default=4)
-</dt>
-<dd>
-<p>
- Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>remoteLsMaxAge</em> (integer, default=60)
-</dt>
-<dd>
-<p>
- Time in seconds after which link state is declared stale if no RA is received.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>mobileAddrMaxAge</em> (integer, default=60)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This value is no longer used in the router.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
-</dt>
-<dd>
-<p>
- The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
-</p>
-</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
-</dt>
-<dd>
-<p>
- A file to dump debugging information that can’t be logged normally.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
-</dt>
-<dd>
-<p>
- Absolute path to the SASL configuration file.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string, default=<em>qdrouterd</em>)
-</dt>
-<dd>
-<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_listener">listener</h3>
-<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
-</dt>
-<dd>
-<p>
- Space separated list of accepted SASL authentication mechanisms.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>authenticatePeer</em> (boolean)
-</dt>
-<dd>
-<p>
- yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requireEncryption</em> (boolean)
-</dt>
-<dd>
-<p>
- yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requireSsl</em> (boolean)
-</dt>
-<dd>
-<p>
- yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>trustedCerts</em> (path)
-</dt>
-<dd>
-<p>
- This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=16384)
-</dt>
-<dd>
-<p>
- Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
-</dt>
-<dd>
-<p>
- The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requirePeerAuth</em> (boolean)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>allowUnsecured</em> (boolean)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>allowNoSasl</em> (boolean)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
-</dt>
-<dd>
-<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
-</p>
-</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
-</dt>
-<dd>
-<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
-</dt>
-<dd>
-<p>
- Unique name optionally assigned by user. Can be changed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
-</dt>
-<dd>
-<p>
- IP address: ipv4 or ipv6 literal or a host name
-</p>
-</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
-</dt>
-<dd>
-<p>
- Port number or symbolic service name.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
-</dt>
-<dd>
-<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
-</dt>
-<dd>
-<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
-</dt>
-<dd>
-<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
-</dt>
-<dd>
-<p>
- name of the sslProfile
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_connector">connector</h3>
-<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
-</dt>
-<dd>
-<p>
- Space separated list of accepted SASL authentication mechanisms.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>allowRedirect</em> (boolean, default=True)
-</dt>
-<dd>
-<p>
- Allow the peer to redirect this connection to another address.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=65536)
-</dt>
-<dd>
-<p>
- Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
-</dt>
-<dd>
-<p>
- The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
-</dt>
-<dd>
-<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
-</p>
-</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
-</dt>
-<dd>
-<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>verifyHostName</em> (boolean, default=True)
-</dt>
-<dd>
-<p>
- yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslUsername</em> (string)
-</dt>
-<dd>
-<p>
- The user name that the connector is using to connect to a peer.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslPassword</em> (string)
-</dt>
-<dd>
-<p>
- The password that the connector is using to connect to a peer.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
-</dt>
-<dd>
-<p>
- Unique name optionally assigned by user. Can be changed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
-</dt>
-<dd>
-<p>
- IP address: ipv4 or ipv6 literal or a host name
-</p>
-</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
-</dt>
-<dd>
-<p>
- Port number or symbolic service name.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
-</dt>
-<dd>
-<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
-</dt>
-<dd>
-<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
-</dt>
-<dd>
-<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
-</dt>
-<dd>
-<p>
- name of the sslProfile
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_log">log</h3>
-<div class="paragraph"><p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>module</em> (One of [<em>ROUTER</em>, <em>ROUTER_CORE</em>, <em>ROUTER_HELLO</em>, <em>ROUTER_LS</em>, <em>ROUTER_MA</em>, <em>MESSAGE</em>, <em>SERVER</em>, <em>AGENT</em>, <em>CONTAINER</em>, <em>ERROR</em>, <em>POLICY</em>, <em>DEFAULT</em>], required)
-</dt>
-<dd>
-<p>
- Module to configure. The special module <em>DEFAULT</em> specifies defaults for all modules.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>enable</em> (string, default=<em>default</em>, required)
-</dt>
-<dd>
-<p>
- Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <em>+</em> to enable that level and above. For example <em>trace,debug,warning+</em> means enable trace, debug, warning, error and critical. The value <em>none</em> means disable logging for the module. The value <em>default</em> means use the value from the DEFAULT module.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>timestamp</em> (boolean)
-</dt>
-<dd>
-<p>
- Include timestamp in log messages.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>source</em> (boolean)
-</dt>
-<dd>
-<p>
- Include source file and line number in log messages.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>output</em> (string)
-</dt>
-<dd>
-<p>
- Where to send log messages. Can be <em>stderr</em>, <em>syslog</em> or a file name.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_fixedaddress">fixedAddress</h3>
-<div class="paragraph"><p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
-</dt>
-<dd>
-<p>
- The address prefix (always starting with <em>/</em>).
-</p>
-</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
-</dt>
-<dd>
-<p>
- The phase of a multi-hop address passing through one or more waypoints.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>fanout</em> (One of [<em>multiple</em>, <em>single</em>], default=<em>multiple</em>)
-</dt>
-<dd>
-<p>
- One of <em>multiple</em> or <em>single</em>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>bias</em> (One of [<em>closest</em>, <em>spread</em>], default=<em>closest</em>)
-</dt>
-<dd>
-<p>
- Only if fanout is single. One of <em>closest</em> or <em>spread</em>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_waypoint">waypoint</h3>
-<div class="paragraph"><p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>address</em> (string, required)
-</dt>
-<dd>
-<p>
- The AMQP address of the waypoint.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>connector</em> (string, required)
-</dt>
-<dd>
-<p>
- The name of the on-demand connector used to reach the waypoint’s container.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>inPhase</em> (integer, default=-1)
-</dt>
-<dd>
-<p>
- The phase of the address as it is routed <em>to</em> the waypoint.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>outPhase</em> (integer, default=-1)
-</dt>
-<dd>
-<p>
- The phase of the address as it is routed <em>from</em> the waypoint.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroutepattern">linkRoutePattern</h3>
-<div class="paragraph"><p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
-</dt>
-<dd>
-<p>
- An address prefix to match against target and source addresses. This pattern must be of the form <em><text>.<text1>.<textN></em> or <em><text></em> or <em><text>.</em> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <em>org.apache</em> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
-</p>
-</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>], default=<em>both</em>)
-</dt>
-<dd>
-<p>
- Link direction for match: <em>in</em> matches only links inbound to the client; <em>out</em> matches only links outbound from the client; <em>both</em> matches any link.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>connector</em> (string)
-</dt>
-<dd>
-<p>
- The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_address">address</h3>
-<div class="paragraph"><p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
-</dt>
-<dd>
-<p>
- The address prefix for the configured settings
-</p>
-</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>multicast</em>, <em>closest</em>, <em>balanced</em>], default=<em>balanced</em>)
-</dt>
-<dd>
-<p>
- Treatment of traffic associated with the address
-</p>
-</dd>
-<dt class="hdlist1">
-<em>waypoint</em> (boolean)
-</dt>
-<dd>
-<p>
- Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>ingressPhase</em> (integer)
-</dt>
-<dd>
-<p>
- Advanced - Override the ingress phase for this address
-</p>
-</dd>
-<dt class="hdlist1">
-<em>egressPhase</em> (integer)
-</dt>
-<dd>
-<p>
- Advanced - Override the egress phase for this address
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroute">linkRoute</h3>
-<div class="paragraph"><p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
-</dt>
-<dd>
-<p>
- The address prefix for the configured settings
-</p>
-</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
-</dt>
-<dd>
-<p>
- ContainerID for the target container
-</p>
-</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
-</dt>
-<dd>
-<p>
- The name from a connector or listener
-</p>
-</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>linkBalanced</em>], default=<em>linkBalanced</em>)
-</dt>
-<dd>
-<p>
- Treatment of traffic associated with the address
-</p>
-</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
-</dt>
-<dd>
-<p>
- The permitted direction of links: <em>in</em> means client senders; <em>out</em> means client receivers
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_autolink">autoLink</h3>
-<div class="paragraph"><p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>addr</em> (string, required)
-</dt>
-<dd>
-<p>
- The address of the provisioned object
-</p>
-</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
-</dt>
-<dd>
-<p>
- The direction of the link to be created. In means into the router, out means out of the router.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
-</dt>
-<dd>
-<p>
- The address phase for this link. Defaults to <em>0</em> for <em>out</em> links and <em>1</em> for <em>in</em> links.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
-</dt>
-<dd>
-<p>
- ContainerID for the target container
-</p>
-</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
-</dt>
-<dd>
-<p>
- The name from a connector or listener
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_console">console</h3>
-<div class="paragraph"><p>Start a websocket/tcp proxy and http file server to serve the web console</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>listener</em> (string)
-</dt>
-<dd>
-<p>
- The name of the listener to send the proxied tcp traffic to.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>wsport</em> (integer, default=5673)
-</dt>
-<dd>
-<p>
- port on which to listen for websocket traffic
-</p>
-</dd>
-<dt class="hdlist1">
-<em>proxy</em> (string)
-</dt>
-<dd>
-<p>
- The full path to the proxy program to run.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>home</em> (string)
-</dt>
-<dd>
-<p>
- The full path to the html/css/js files for the console.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>args</em> (string)
-</dt>
-<dd>
-<p>
- Optional args to pass the proxy program for logging, authentication, etc.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policy">policy</h3>
-<div class="paragraph"><p>Defines global connection limit</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maximumConnections</em> (integer)
-</dt>
-<dd>
-<p>
- Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>enableAccessRules</em> (boolean)
-</dt>
-<dd>
-<p>
- Enable user rule set processing and connection denial.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>policyFolder</em> (path)
-</dt>
-<dd>
-<p>
- The absolute path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>defaultApplication</em> (string)
-</dt>
-<dd>
-<p>
- Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>defaultApplicationEnabled</em> (boolean)
-</dt>
-<dd>
-<p>
- Enable defaultApplication policy fallback logic.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policyruleset">policyRuleset</h3>
-<div class="paragraph"><p>Per application definition of the locations from which users may connect and the groups to which users belong.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maxConnections</em> (integer)
-</dt>
-<dd>
-<p>
- Maximum number of concurrent client connections allowed. Zero implies no limit.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>maxConnPerUser</em> (integer)
-</dt>
-<dd>
-<p>
- Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>maxConnPerHost</em> (integer)
-</dt>
-<dd>
-<p>
- Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>userGroups</em> (map)
-</dt>
-<dd>
-<p>
- A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed <em>restricted</em>. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>ingressHostGroups</em> (map)
-</dt>
-<dd>
-<p>
- A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address <em>*</em> represents any host address.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>ingressPolicies</em> (map)
-</dt>
-<dd>
-<p>
- A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>connectionAllowDefault</em> (boolean)
-</dt>
-<dd>
-<p>
- Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <em>default</em> user group and receive <em>default</em> settings.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>settings</em> (map)
-</dt>
-<dd>
-<p>
- A map where each key is a user group name and the value is a map of the corresponding settings for that group.
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:42:34 EDT
-</div>
-</div>
-</body>
-</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[06/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/book.html
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/book.html b/input/releases/qpid-dispatch-master/book.html
deleted file mode 100644
index 64014d3..0000000
--- a/input/releases/qpid-dispatch-master/book.html
+++ /dev/null
@@ -1,4406 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>Qpid Dispatch Router Book</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install(2);
-/*]]>*/
-</script>
-</head>
-<body class="book">
-<div id="header">
-<h1>Qpid Dispatch Router Book</h1>
-<div id="toc">
- <div id="toctitle">Table of Contents</div>
- <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="introduction">1. Introduction</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="overview">1.1. Overview</h3>
-<div class="paragraph"><p>The Dispatch router is an AMQP message router that provides
-advanced interconnect capabilities. It allows flexible routing of
-messages between any AMQP-enabled endpoints, whether they be clients,
-servers, brokers or any other entity that can send or receive standard
-AMQP messages.</p></div>
-<div class="paragraph"><p>A messaging client can make a single AMQP connection into a messaging
-bus built of Dispatch routers and, over that connection, exchange
-messages with one or more message brokers, and at the same time exchange
-messages directly with other endpoints without involving a broker at
-all.</p></div>
-<div class="paragraph"><p>The router is an intermediary for messages but it is <em>not</em> a broker. It
-does not <em>take responsibility for</em> messages. It will, however, propagate
-settlement and disposition across a network such that delivery
-guarantees are met. In other words: the router network will deliver the
-message, possibly via several intermediate routers, <em>and</em> it will route
-the acknowledgement of that message by the ultimate receiver back across
-the same path. This means that <em>responsibility</em> for the message is
-transfered from the original sender to the ultimate receiver <em>as if
-they were directly connected</em>. However this is done via a flexible
-network that allows highly configurable routing of the message
-transparent to both sender and receiver.</p></div>
-<div class="paragraph"><p>There are some patterns where this enables "brokerless messaging"
-approaches that are preferable to brokered approaches. In other cases a
-broker is essential (in particular where you need the separation of
-responsibility and/or the buffering provided by store-and-forward) but a
-dispatch network can still be useful to tie brokers and clients together
-into patterns that are difficult with a single broker.</p></div>
-<div class="paragraph"><p>For a "brokerless" example, consider the common brokered implementation
-of the request-response pattern, a client puts a request on a queue and
-then waits for a reply on another queue. In this case the broker can be
-a hindrance - the client may want to know immediatly if there is nobody
-to serve the request, but typically it can only wait for a timeout to
-discover this. With a dispatch network, the client can be informed
-immediately if its message cannot be delivered because nobody is
-listening. When the client receives acknowledgement of the request it
-knows not just that it is sitting on a queue, but that it has actually
-been received by the server.</p></div>
-<div class="paragraph"><p>For an exampe of using dispatch to enhance the use of brokers, consider
-using an array of brokers to implement a scalable distributed work
-queue. A dispatch network can make this appear as a single queue, with
-senders publishing to a single address and receivers subscribing to a
-single address. The dispatch network can distribute work to any broker
-in the array and collect work from any broker for any receiver. Brokers
-can be shut down or added without affecting clients. This elegantly
-solves the common difficulty of "stuck messages" when implementing this
-pattern with brokers alone. If a receiver is connected to a broker that
-has no messages, but there are messages on another broker, you have to
-somehow transfer them or leave them "stuck". With a dispatch network,
-<em>all</em> the receivers are connected to <em>all</em> the brokers. If there is a
-message anywhere it can be delivered to any receiver.</p></div>
-<div class="paragraph"><p>The router is meant to be deployed in topologies of multiple routers,
-preferably with redundant paths. It uses link-state routing protocols
-and algorithms (similar to OSPF or IS-IS from the networking world) to
-calculate the best path from every point to every other point and to
-recover quickly from failures. It does not need to use clustering for
-high availability; rather, it relies on redundant paths to provide
-continued connectivity in the face of system or network failure. Because
-it never takes responsibility for messages it is effectively stateless.
-Messages not delivered to their final destination will not be
-acknowledged to the sender and therefore the sender can re-send such
-messages if it is disconnected from the network.</p></div>
-</div>
-<div class="sect2">
-<h3 id="benefits">1.2. Benefits</h3>
-<div class="paragraph"><p>Simplifies connectivity</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-An endpoint can do all of its messaging through a single transport
-connection
-</p>
-</li>
-<li>
-<p>
-Avoid opening holes in firewalls for incoming connections
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Provides messaging connectivity where there is no TCP/IP connectivity</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-A server or broker can be in a private IP network (behind a NAT
-firewall) and be accessible by messaging endpoints in other networks
-(learn more).
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>Simplifies reliability</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Reliability and availability are provided using redundant topology,
-not server clustering
-</p>
-</li>
-<li>
-<p>
-Reliable end-to-end messaging without persistent stores
-</p>
-</li>
-<li>
-<p>
-Use a message broker only when you need store-and-forward semantics
-</p>
-</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="features">1.3. Features</h3>
-<div class="ulist"><ul>
-<li>
-<p>
-Can be deployed stand-alone or in a network of routers
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Supports arbitrary network topology - no restrictions on redundancy
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Automatic route computation - adjusts quickly to changes in topology
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-</li>
-<li>
-<p>
-Provides remote access to brokers or other AMQP servers
-</p>
-</li>
-<li>
-<p>
-Security
-</p>
-</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="using-qpid-dispatch">2. Using Qpid Dispatch</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="configuration">2.1. Configuration</h3>
-<div class="paragraph"><p>The default configuration file is installed in
-<em>install-prefix/etc/qpid-dispatch/qdrouterd.conf</em>. 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></div>
-<div class="paragraph"><p>To run the router, invoke the executable: qdrouterd [-c my-config-file]</p></div>
-<div class="paragraph"><p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
-page.</p></div>
-</div>
-<div class="sect2">
-<h3 id="tools">2.2. Tools</h3>
-<div class="sect3">
-<h4 id="qdstat">2.2.1. qdstat</h4>
-<div class="paragraph"><p><em>qdstat</em> is a command line tool that lets you view the status of a
-Dispatch Router. The following options are useful for seeing what the
-router is doing:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="17%" />
-<col width="83%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Option</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table">-l</p></td>
-<td align="left" valign="top"><p class="table">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
-routbers.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">-a</p></td>
-<td align="left" valign="top"><p class="table">Print a list of addresses known to the router.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">-n</p></td>
-<td align="left" valign="top"><p class="table">Print a list of known routers in the network.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">-c</p></td>
-<td align="left" valign="top"><p class="table">Print a list of connections to the router.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">--autolinks</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configured auto-links.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">--linkroutes</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configures link-routes.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-<div class="paragraph"><p>For complete details see the <em>qdstat(8)</em> man page and the output of
-<code>qdstat --help</code>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="qdmanage">2.2.2. qdmanage</h4>
-<div class="paragraph"><p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
-to not only view but modify the configuration of a running dispatch
-router.</p></div>
-<div class="paragraph"><p>For example you can query all the connection entities in the router:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdmanage query --type connection</code></pre>
-</div></div>
-<div class="paragraph"><p>To enable logging debug and higher level messages by default:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdmanage update log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="paragraph"><p>In fact, everything that can be configured in the configuration file can
-also be created in a running router via management. For example to
-create a new listener in a running router:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdmanage create type=listener port=5555</code></pre>
-</div></div>
-<div class="paragraph"><p>Now you can connect to port 5555, for exampple:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdmanage query -b localhost:5555 --type listener</code></pre>
-</div></div>
-<div class="paragraph"><p>For complete details see the <em>qdmanage(8)</em> man page and the output of
-<code>qdmanage --help</code>. Also for details of what can be configured see the
-<em>qdrouterd.conf(5)</em> man page.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="basic-usage-and-examples">2.3. Basic Usage and Examples</h3>
-<div class="sect3">
-<h4 id="standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</h4>
-<div class="paragraph"><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></div>
-<div class="paragraph"><p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
-like the following:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat -a
-Router Addresses
- class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
- ===============================================================================================================
- local $_management_internal closest 1 0 0 0 0 0 0 0 0
- local $displayname closest 1 0 0 0 0 0 0 0 0
- mobile $management 0 closest 1 0 0 0 1 0 0 1 0
- local $management closest 1 0 0 0 0 0 0 0 0
- local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that there are a number of known addresses. <em>$management</em> is the
-address of the router’s embedded management agent.
-<em>temp.1GThUllfR7N+BDP</em> is the temporary reply-to address of the <em>qdstat</em>
-client making requests to the agent.</p></div>
-<div class="paragraph"><p>If you change the mode to interior and restart the processs, the same
-command will yield additional addresses which are used for inter-router
-communication:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat -a
-Router Addresses
- class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
- =================================================================================================================
- local $_management_internal closest 1 0 0 0 0 0 0 0 0
- local $displayname closest 1 0 0 0 0 0 0 0 0
- mobile $management 0 closest 1 0 0 0 1 0 0 1 0
- local $management closest 1 0 0 0 0 0 0 0 0
- local qdhello flood 1 0 0 0 0 0 0 0 10
- local qdrouter flood 1 0 0 0 0 0 0 0 0
- topo qdrouter flood 1 0 0 0 0 0 0 0 1
- local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
- topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
- local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="mobile-subscribers">2.3.2. Mobile Subscribers</h4>
-<div class="paragraph"><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></div>
-<div class="paragraph"><p>To illustrate a subscription on a stand-alone router, you can use the
-examples that are provided with Qpid Proton. Using the <em>simple_recv.py</em>
-example receiver:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ python ./simple_recv.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-<div class="paragraph"><p>This command creates a receiving link subscribed to the specified
-address. To verify the subscription:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat -a
-Router Addresses
- class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
- ===============================================================================================================
- local $_management_internal closest 1 0 0 0 0 0 0 0 0
- local $displayname closest 1 0 0 0 0 0 0 0 0
- mobile $management 0 closest 1 0 0 0 2 0 0 2 0
- local $management closest 1 0 0 0 0 0 0 0 0
- mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
- local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>You can then, in a separate command window, run a sender to produce
-messages to that address:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ python ./simple_send.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-reply-to">2.3.3. Dynamic Reply-To</h4>
-<div class="paragraph"><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></div>
-<div class="listingblock">
-<div class="content">
-<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>
-</div></div>
-<div class="paragraph"><p>The equivalent program written in Python against the Proton Messenger
-API:</p></div>
-<div class="listingblock">
-<div class="content">
-<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>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="link-routing">2.4. Link Routing</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.4. This feature was
-significantly updated in Qpid Dispatch 0.6.</p></div>
-<div class="paragraph"><p>Link-routing is an alternative strategy for routing messages across a
-network of routers. With the existing message-routing strategy, each
-router makes a routing decision on a per-message basis when the message
-is delivered. Link-routing is different because it makes routing
-decisions when link-attach frames arrive. A link is effectively chained
-across the network of routers from the establishing node to the
-destination node. Once the link is established, the transfer of message
-deliveries, flow frames, and dispositions is performed across the routed
-link.</p></div>
-<div class="paragraph"><p>The main benefit to link-routing is that endpoints can use the full link
-protocol to interact with other endpoints in far-flung parts of the
-network. For example, a client can establish a receiver across the
-network to a queue on a remote broker and use link credit to control
-the flow of messages from the broker. Similarly, a receiver can
-establish a link to a topic on a remote broker using a server-side
-filter.</p></div>
-<div class="paragraph"><p>Why would one want to do this? One reason is to provide client
-isolation. A network like the following can be deployed:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code> Public Network
- +-----------------+
- | +-----+ |
- | B1 | Rp | |
- | +/--\-+ |
- | / \ |
- | / \ |
- +----/--------\---+
- / \
- / \
- / \
- Private Net A / \ Private Net B
- +--------------/--+ +---\-------------+
- | +---/-+ | | +--\--+ |
- | B2 | Ra | | | | Rb | C1 |
- | +-----+ | | +-----+ |
- | | | |
- | | | |
- +-----------------+ +-----------------+</code></pre>
-</div></div>
-<div class="paragraph"><p>The clients in Private Net B can be constrained (by firewall policy)
-to only connect to the Router in their own network. Using
-link-routing, these clients can access queues, topics, and other AMQP
-services that are in the Public Network or even in Private Net A.</p></div>
-<div class="paragraph"><p>For example, The router Ra can be configured to expose queues in
-broker B2 to the network. Client C1 can then establish a connection
-to Rb, the local router, open a subscribing link to "b2.event-queue",
-and receive messages stored on that queue in broker B2.</p></div>
-<div class="paragraph"><p>C1 is unable to create a TCP/IP connection to B1 because of its
-isolation (and because B2 is itself in a private network). However, with
-link routing, C1 can interact with B2 using the AMQP link protocol.</p></div>
-<div class="paragraph"><p>Note that in this case, neither C1 nor B2 have been modified in any way
-and neither need be aware of the fact that there is a message-router
-network between them.</p></div>
-<div class="sect3">
-<h4 id="link-routing-configuration">2.4.1. Configuration</h4>
-<div class="paragraph"><p>Starting with the configured topology shown above, how is link-routing
-configured to support the example described above?</p></div>
-<div class="paragraph"><p>First, router Ra needs to be told how to make a connection to the broker
-B2:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>connector {
- name: broker
- role: route-container
- host: <B2-url>
- port: <B2-port>
- saslMechanisms: ANONYMOUS
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>This <em>route-container</em> connector tells the router how to connect to an
-external AMQP container when it is needed. The name "broker" will be
-used later to refer to this connection.</p></div>
-<div class="paragraph"><p>Now, the router must be configured to route certain addresses to B2:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>linkRoute {
- prefix: b2
- dir: in
- connection: broker
-}
-
-linkRoute {
- prefix: b2
- dir: out
- connection: broker
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>The linkRoute tells router Ra that any sender or receiver that is
-attached with a target or source (respectively) whos address begins with
-"b2", should be routed to the broker B2 (via the route-container
-connector).</p></div>
-<div class="paragraph"><p>Note that receiving and sending links are configured and routed
-separately. This allows configuration of link routes for listeners only
-or senders only. A direction of "in" matches client senders (i.e. links
-that carry messages inbound to the router network). Direction "out"
-matches client receivers.</p></div>
-<div class="paragraph"><p>Examples of addresses that "begin with <em>b2</em>" include:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-b2
-</p>
-</li>
-<li>
-<p>
-b2.queues
-</p>
-</li>
-<li>
-<p>
-b2.queues.app1
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>When the route-container connector is configured, router Ra establishes
-a connection to the broker. Once the connection is open, Ra tells the
-other routers (Rp and Rb) that it is a valid destination for link-routes
-to the "b2" prefix. This means that sender or receiver links attached to
-Rb or Rp will be routed via the shortest path to Ra where they are then
-routed outbound to the broker B2.</p></div>
-<div class="paragraph"><p>On Rp and Rb, it is advisable to add the identical configuration. It is
-permissible for a linkRoute configuration to reference a connection that
-does not exist.</p></div>
-<div class="paragraph"><p>This configuration tells the routers that link-routing is intended to be
-available for targets and sources starting with "b2". This is important
-because it is possible that B2 might be unavailable or shut off. If B2
-is unreachable, Ra will not advertize itself as a destination for "b2"
-and the other routers might never know that "b2" was intended for
-link-routing.</p></div>
-<div class="paragraph"><p>The above configuration allows Rb and Rp to reject attaches that should
-be routed to B2 with an error message that indicates that there is no
-route available to the destination.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="indirect-waypoints-and-auto-links">2.5. Indirect Waypoints and Auto-Links</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
-improvement on an earlier somewhat experimental feature called
-Waypoints.</p></div>
-<div class="paragraph"><p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
-actively attach a link to a node on an external AMQP container. The
-obvious application for this feature is to route messages through a
-queue on a broker, but other applications are possible as well.</p></div>
-<div class="paragraph"><p>An auto-link manages the lifecycle of one AMQP link. If messages are to
-be routed to and from a queue on a broker, then two auto-links are
-needed: one for sending messages to the queue and another for receiving
-messages from the queue. The container to which an auto-link attempts to
-attach may be identified in one of two ways:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="ulist"><ul>
-<li>
-<p>
-The name of the connector/listener that resulted in the connection of
-the container, or
-</p>
-</li>
-<li>
-<p>
-The AMQP container-id of the remote container.
-</p>
-</li>
-</ul></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="sect3">
-<h4 id="queue-waypoint-example">2.5.1. Queue Waypoint Example</h4>
-<div class="paragraph"><p>Here is an example configuration for routing messages deliveries through
-a pair of queues on a broker:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>connector {
- name: broker
- role: route-container
- host: <hostname>
- port: <port>
- saslMechanisms: ANONYMOUS
-}
-
-address {
- prefix: queue
- waypoint: yes
-}
-
-autoLink {
- addr: queue.first
- dir: in
- connection: broker
-}
-
-autoLink {
- addr: queue.first
- dir: out
- connection: broker
-}
-
-autoLink {
- addr: queue.second
- dir: in
- connection: broker
-}
-
-autoLink {
- addr: queue.second
- dir: out
- connection: broker
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
-for routing messages through queues via autolinks. The four <code>autoLink</code> entities
-identify the head and tail of two queues on the broker that will be connected
-via auto-links.</p></div>
-<div class="paragraph"><p>If there is no broker connected, the auto-links shall remain
-<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat --autolinks
-AutoLinks
- addr dir phase link status lastErr
- ===================================================
- queue.first in 1 inactive
- queue.first out 0 inactive
- queue.second in 1 inactive
- queue.second out 0 inactive</code></pre>
-</div></div>
-<div class="paragraph"><p>If a broker comes online with a queue called <em>queue.first</em>, the
-auto-links will attempt to activate:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat --autolinks
-AutoLinks
- addr dir phase link status lastErr
- ======================================================================
- queue.first in 1 6 active
- queue.first out 0 7 active
- queue.second in 1 failed Node not found: queue.second
- queue.second out 0 failed Node not found: queue.second</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that two of the auto-links are in <em>failed</em> state because the queue
-does not exist on the broker.</p></div>
-<div class="paragraph"><p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
-three messages to <em>queue.first</em> via the router:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ python simple_send.py -a 127.0.0.1/queue.first -m3
-all messages confirmed</code></pre>
-</div></div>
-<div class="paragraph"><p>and then look at the address statistics on the router:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat -a
-Router Addresses
- class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
- ========================================================================================================
- mobile queue.first 1 balanced 0 0 0 0 0 0 0 0 0
- mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>we see that <em>queue.first</em> appears twice in the list of addresses. The
-<code>phs</code>, or phase column shows that there are two phases for the
-address. Phase <em>0</em> is for routing message deliveries from producers to
-the tail of the queue (the <code>out</code> auto-link associated with the queue).
-Phase 1 is for routing deliveries from the head of the queue to
-subscribed consumers.</p></div>
-<div class="paragraph"><p>Note that three deliveries have been counted in the "in" and "out"
-columns for phase <em>0</em>. The "in" column represents the three messages
-that arrived from <code>simple_send.py</code> and the <code>out</code> column represents the three
-deliveries to the queue on the broker.</p></div>
-<div class="paragraph"><p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ python simple_recv.py -a 127.0.0.1:5672/queue.first -m3
-{u'sequence': int32(1)}
-{u'sequence': int32(2)}
-{u'sequence': int32(3)}</code></pre>
-</div></div>
-<div class="paragraph"><p>We receive the three queued messages. Looking at the addresses again, we
-see that phase 1 was used to deliver those messages from the queue to
-the consumer.</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>$ qdstat -a
-Router Addresses
- class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
- ========================================================================================================
- mobile queue.first 1 balanced 0 0 0 0 3 3 0 0 0
- mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that even in a multi-router network, and with multiple producers
-and consumers for <em>queue.first</em>, all deliveries will be routed through
-the queue on the connected broker.</p></div>
-</div>
-<div class="sect3">
-<h4 id="sharded-queue-example">2.5.2. Sharded Queue Example</h4>
-<div class="paragraph"><p>Here is an extension of the above example to illustrate how Qpid
-Dispatch Router can be used to create a distributed queue in which
-multiple brokers share the message-queueing load.</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>connector {
- name: broker1
- role: route-container
- host: <hostname>
- port: <port>
- saslMechanisms: ANONYMOUS
-}
-
-connector {
- name: broker2
- role: route-container
- host: <hostname>
- port: <port>
- saslMechanisms: ANONYMOUS
-}
-
-address {
- prefix: queue
- waypoint: yes
-}
-
-autoLink {
- addr: queue.first
- dir: in
- connection: broker1
-}
-
-autoLink {
- addr: queue.first
- dir: out
- connection: broker1
-}
-
-autoLink {
- addr: queue.first
- dir: in
- connection: broker2
-}
-
-autoLink {
- addr: queue.first
- dir: out
- connection: broker2
-}</code></pre>
-</div></div>
-<div class="paragraph"><p>In the above configuration, there are two instances of <em>queue.first</em> on
-brokers 1 and 2. Message traffic from producers to address <em>queue.first</em>
-shall be balanced between the two instance and messages from the queues
-shall be balanced across the collection of subscribers to the same
-address.</p></div>
-</div>
-<div class="sect3">
-<h4 id="dynamically-adding-shards">2.5.3. Dynamically Adding Shards</h4>
-<div class="paragraph"><p>Since configurable entities in the router can also be accessed via the
-management protocol, we can remotely add a shard to the above example
-using <code>qdmanage</code>:</p></div>
-<div class="listingblock">
-<div class="content">
-<pre><code>qdmanage create --type org.apache.qpid.dispatch.connector host=<host> port=<port> name=broker3
-qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=in connection=broker3
-qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=out connection=broker3</code></pre>
-</div></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="technical-details-and-specifications">3. Technical Details and Specifications</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="client-compatibility">3.1. Client Compatibility</h3>
-<div class="paragraph"><p>Dispatch Router should, in theory, work with any client that is
-compatible with AMQP 1.0. The following clients have been tested:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="22%" />
-<col width="78%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Client</em> </th>
-<th align="left" valign="top"><em>Notes</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table">qpid::messaging</p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Proton Reactor</p></td>
-<td align="left" valign="top"><p class="table">The Proton Reactor API is compatible with Dispatch
-Router.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">Proton Messenger</p></td>
-<td align="left" valign="top"><p class="table">Messenger works with Dispatch Router.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect2">
-<h3 id="addressing">3.2. Addressing</h3>
-<div class="paragraph"><p>AMQP addresses are used to control the flow of messages across a network
-of routers. Addresses are used in a number of different places in the
-AMQP 1.0 protocol. They can be used in a specific message in the <code>to</code>
-and <code>reply-to</code> fields of a message’s properties. They are also used
-during the creation of links in the <code>address</code> field of a <code>source</code> or
-a <code>target</code>.</p></div>
-<div class="paragraph"><p>Addresses designate various kinds of entities in a messaging network:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-Endpoint processes that consume data or offer a service
-</p>
-</li>
-<li>
-<p>
-Topics that match multiple consumers to multiple producers
-</p>
-</li>
-<li>
-<p>
-Entities within a messaging broker:
-</p>
-<div class="ulist"><ul>
-<li>
-<p>
-Queues
-</p>
-</li>
-<li>
-<p>
-Durable Topics
-</p>
-</li>
-<li>
-<p>
-Exchanges
-</p>
-</li>
-</ul></div>
-</li>
-</ul></div>
-<div class="paragraph"><p>The syntax of an AMQP address is opaque as far as the router network is
-concerned. A syntactical structure may be used by the administrator that
-creates addresses, but the router treats them as opaque strings. Routers
-consider addresses to be mobile such that any address may be directly
-connected to any router in a network and may move around the topology.
-In cases where messages are broadcast to or balanced across multiple
-consumers, an address may be connected to multiple routers in the
-network.</p></div>
-<div class="paragraph"><p>Addresses have semantics associated with them. When an address is
-created in the network, it is assigned a set of semantics (and access
-rules) during a process called provisioning. The semantics of an address
-control how routers behave when they see the address being used.</p></div>
-<div class="paragraph"><p>Address semantics include the following considerations:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-<em>Routing pattern</em> - direct, multicast, balanced
-</p>
-</li>
-<li>
-<p>
-<em>Undeliverable action</em> - drop, hold and retry, redirect
-</p>
-</li>
-<li>
-<p>
-<em>Reliability</em> - N destinations, etc.
-</p>
-</li>
-</ul></div>
-<div class="sect3">
-<h4 id="routing-patterns">3.2.1. Routing patterns</h4>
-<div class="paragraph"><p>Routing patterns constrain the paths that a message can take across a
-network.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="18%" />
-<col width="82%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><em>Direct</em></p></td>
-<td align="left" valign="top"><p class="table">Direct routing allows for only one consumer to use an address
-at a time. Messages (or links) follow the lowest cost path across the
-network from the sender to the one receiver.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><em>Multicast</em></p></td>
-<td align="left" valign="top"><p class="table">Multicast routing allows multiple consumers to use the
-same address at the same time. Messages are routed such that each
-consumer receives a copy of the message.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><em>Balanced</em></p></td>
-<td align="left" valign="top"><p class="table">Balanced routing also allows multiple consumers to use the
-same address. In this case, messages are routed to exactly one of the
-consumers, and the network attempts to balance the traffic load across
-the set of consumers using the same address.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="routing-mechanisms">3.2.2. Routing mechanisms</h4>
-<div class="paragraph"><p>The fact that addresses can be used in different ways suggests that
-message routing can be accomplished in different ways. Before going into
-the specifics of the different routing mechanisms, it would be good to
-first define what is meant by the term <em>routing</em>:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="paragraph"><p>In a network built of multiple routers connected by connections (i.e.,
-nodes and edges in a graph), <em>routing</em> determines which connection to
-use to send a message directly to its destination or one step closer to
-its destination.</p></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="paragraph"><p>Each router serves as the terminus of a collection of incoming and
-outgoing links. The links either connect directly to endpoints that
-produce and consume messages, or they connect to other routers in the
-network along previously established connections.</p></div>
-<div class="sect4">
-<h5 id="message-routing">Message routing</h5>
-<div class="paragraph"><p>Message routing occurs upon delivery of a message and is done based on
-the address in the message’s <code>to</code> field.</p></div>
-<div class="paragraph"><p>When a delivery arrives on an incoming link, the router extracts the
-address from the delivered message’s <code>to</code> field and looks the address up
-in its routing table. The lookup results in zero or more outgoing links
-onto which the message shall be resent.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="20%" />
-<col width="80%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Delivery</em> </th>
-<th align="left" valign="top"><em>Handling</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><em>pre-settled</em></p></td>
-<td align="left" valign="top"><p class="table">If the arriving delivery is pre-settled (i.e., fire and
-forget), the incoming delivery shall be settled by the router, and the
-outgoing deliveries shall also be pre-settled. In other words, the
-pre-settled nature of the message delivery is propagated across the
-network to the message’s destination.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><em>unsettled</em></p></td>
-<td align="left" valign="top"><p class="table">Unsettled delivery is also propagated across the network.
-Because unsettled delivery records cannot be discarded, the router
-tracks the incoming deliveries and keeps the association of the incoming
-deliveries to the resulting outgoing deliveries. This kept association
-allows the router to continue to propagate changes in delivery state
-(settlement and disposition) back and forth along the path which the
-message traveled.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="amqp-mapping">3.3. AMQP Mapping</h3>
-<div class="paragraph"><p>Dispatch Router is an AMQP router and as such, it provides extensions,
-code-points, and semantics for routing over AMQP. This page documents the
-details of Dispatch Router’s use of AMQP.</p></div>
-<div class="sect3">
-<h4 id="message-annotations">3.3.1. Message Annotations</h4>
-<div class="paragraph"><p>The following Message Annotation fields are defined by Dispatch Router:</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="19%" />
-<col width="58%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Field</em> </th>
-<th align="left" valign="top"><em>Type</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.ingress</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.trace</p></td>
-<td align="left" valign="top"><p class="table">list of string</p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.to</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.phase</p></td>
-<td align="left" valign="top"><p class="table">integer</p></td>
-<td align="left" valign="top"><p class="table">The address-phase, if not zero, for messages
-flowing between routers.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="sourcetarget-capabilities">3.3.2. Source/Target Capabilities</h4>
-<div class="paragraph"><p>The following Capability values are used in Sources and Targets.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="19%" />
-<col width="81%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Capability</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table">qd.router</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that are
-used for inter-router message exchange. This capability denotes a link
-used for router-control messages flowing between routers.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table">qd.router-data</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that
-are used for inter-router message exchange. This capability denotes a
-link used for user messages being message-routed across an inter-router
-connection.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-node-properties">3.3.3. Dynamic-Node-Properties</h4>
-<div class="paragraph"><p>The following dynamic-node-properties are used by Dispatch in Sources.</p></div>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="77%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Property</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.address</p></td>
-<td align="left" valign="top"><p class="table">The node address describing the destination desired
-for a dynamic source. If this is absent, the router will terminate any
-dynamic receivers. If this address is present, the router will use the
-address to route the dynamic link attach to the proper destination
-container.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect3">
-<h4 id="addresses-and-address-formats">3.3.4. Addresses and Address Formats</h4>
-<div class="paragraph"><p>The following AMQP addresses and address patterns are used within
-Dispatch Router.</p></div>
-<div class="sect4">
-<h5 id="address-patterns">Address Patterns</h5>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="38%" />
-<col width="62%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_local/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">An address that references a locally attached endpoint.
-Messages using this address pattern shall not be routed over more than
-one link.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/<router>/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">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.</p>
-<p class="table">The <em>0</em> component immediately preceding the router-id is a placeholder
-for an <em>area</em> which may be used in the future if area routing is
-implemented.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code><addr></code></p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-<div class="sect4">
-<h5 id="supported-addresses">Supported Addresses</h5>
-<div class="tableblock">
-<table rules="all"
-width="100%"
-frame="border"
-cellspacing="0" cellpadding="4">
-<col width="36%" />
-<col width="64%" />
-<thead>
-<tr>
-<th align="left" valign="top"><em>Address</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
-</tr>
-</thead>
-<tbody>
-<tr>
-<td align="left" valign="top"><p class="table"><code>$management</code></p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/$management</code></p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdhello</code></p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
-This address is used by a router to communicate with other routers in
-the network.</p></td>
-</tr>
-<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">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.</p></td>
-</tr>
-</tbody>
-</table>
-</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</h4>
-<div class="paragraph"><p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
-emerging AMQP Management specification (draft 9).</p></div>
-<div class="paragraph"><p>Differences from the specification:</p></div>
-<div class="ulist"><ul>
-<li>
-<p>
-The <code>name</code> attribute is not required when an entity is created. If
- not supplied it will be set to the same value as the system-generated
- "identity" attribute. Otherwise it is treated as per the standard.
-</p>
-</li>
-<li>
-<p>
-The <code>REGISTER</code> and <code>DEREGISTER</code> operations are not implemented. The router
- automatically discovers peer routers via the router network and makes
- their management addresses available via the standard <code>GET-MGMT-NODES</code>
- operation.
-= Management Schema
-</p>
-</li>
-</ul></div>
-<div class="paragraph"><p>This chapter documents the set of <strong>management entity types</strong> that define
-configuration and management of a Dispatch Router. A management entity type has
-a set of <strong>attributes</strong> that can be read, some attributes can also be
-updated. Some entity types also support <strong>operations</strong> that can be called.</p></div>
-<div class="paragraph"><p>All management entity types have the following standard attributes:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-type
-</dt>
-<dd>
-<p>
- The fully qualified type of the entity,
- e.g. <code>org.apache.qpid.dispatch.router</code>. This document uses the short name
- without the <code>org.apache.qpid.dispatch</code> prefix e.g. <code>router</code>. The dispatch
- tools will accept the short or long name.
-</p>
-</dd>
-<dt class="hdlist1">
-name
-</dt>
-<dd>
-<p>
- A user-generated identity for the entity. This can be used in other entities
- that need to refer to the named entity.
-</p>
-</dd>
-<dt class="hdlist1">
-identity
-</dt>
-<dd>
-<p>
- A system-generated identity of the entity. It includes
- the short type name and some identifying information. E.g. <code>log/AGENT</code> or
- <code>listener/localhost:amqp</code>
-</p>
-</dd>
-</dl></div>
-<div class="paragraph"><p>There are two main categories of management entity type.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-Configuration Entities
-</dt>
-<dd>
-<p>
- Parameters that can be set in the configuration file
- (see <code>qdrouterd.conf(5)</code> man page) or set at run-time with the <code>qdmanage(8)</code>
- tool.
-</p>
-</dd>
-<dt class="hdlist1">
-Operational Entities
-</dt>
-<dd>
-<p>
- Run-time status values that can be queried using <code>qdstat(8)</code> or <code>qdmanage(8)</code> tools.
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_configuration_entities">3.4. Configuration Entities</h3>
-<div class="paragraph"><p>Configuration entities define the attributes allowed in the configuration file
-(see <code>qdrouterd.conf(5)</code>) but you can also create entities once the router is
-running using the <code>qdrouterd(8)</code> tool’s <code>create</code> operation. Some entities can also
-be modified using the <code>update</code> operation, see the entity descriptions below.</p></div>
-<div class="sect3">
-<h4 id="_container">3.4.1. container</h4>
-<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
-<div class="paragraph"><p>Operations allowed: <code>READ</code></p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>containerName</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
-</p>
-</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- A file to dump debugging information that can’t be logged normally.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Absolute path to the SASL configuration file.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect3">
-<h4 id="_router">3.4.2. router</h4>
-<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
-<div class="paragraph"><p>Operations allowed: <code>READ</code></p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>routerId</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
-</p>
-</dd>
-<dt class="hdlist1">
-<em>id</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
-</p>
-</dd>
-<dt class="hdlist1">
-<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>area</em> (string)
-</dt>
-<dd>
-<p>
- Unused placeholder.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>helloInterval</em> (integer, default=1, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Interval in seconds between HELLO messages sent to neighbor routers.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>helloMaxAge</em> (integer, default=3, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Time in seconds after which a neighbor is declared lost if no HELLO is received.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>raInterval</em> (integer, default=30, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Interval in seconds between Router-Advertisements sent to all routers in a stable network.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>raIntervalFlux</em> (integer, default=4, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>remoteLsMaxAge</em> (integer, default=60, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Time in seconds after which link state is declared stale if no RA is received.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>mobileAddrMaxAge</em> (integer, default=60, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This value is no longer used in the router.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>addrCount</em> (integer)
-</dt>
-<dd>
-<p>
- Number of addresses known to the router.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>linkCount</em> (integer)
-</dt>
-<dd>
-<p>
- Number of links attached to the router node.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>nodeCount</em> (integer)
-</dt>
-<dd>
-<p>
- Number of known peer router nodes.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
-</p>
-</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- A file to dump debugging information that can’t be logged normally.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Absolute path to the SASL configuration file.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string, default=<em>qdrouterd</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect3">
-<h4 id="_listener">3.4.3. listener</h4>
-<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
-<div class="paragraph"><p>Operations allowed: <code>CREATE</code>, <code>DELETE</code>, <code>READ</code></p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>addr</em> (string, default=<em>127.0.0.1</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
-</p>
-</dd>
-<dt class="hdlist1">
-<em>host</em> (string, default=<em>127.0.0.1</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- IP address: ipv4 or ipv6 literal or a host name
-</p>
-</dd>
-<dt class="hdlist1">
-<em>port</em> (string, default=<em>amqp</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Port number or symbolic service name.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>], <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>], default=<em>normal</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer, default=<em>1</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>certDb</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
-</p>
-</dd>
-<dt class="hdlist1">
-<em>certFile</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>keyFile</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the PEM-formatted private key for the above certificate.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>passwordFile</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>password</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>uidFormat</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
-</p>
-</dd>
-<dt class="hdlist1">
-<em>displayNameFile</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The absolute path to the file containing the unique id to dispay name mapping
-</p>
-</dd>
-<dt class="hdlist1">
-<em>sslProfileName</em> (string)
-</dt>
-<dd>
-<p>
- The name of the ssl profile. This is for internal use only. Use the <em>name</em> attribute to assign a name to an sslProfile section
-</p>
-</dd>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Space separated list of accepted SASL authentication mechanisms.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>authenticatePeer</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requireEncryption</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requireSsl</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>trustedCerts</em> (path, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=16384, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>requirePeerAuth</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>allowUnsecured</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>allowNoSasl</em> (boolean, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
-</p>
-</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
-</p>
-</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
-</p>
-</dd>
-</dl></div>
-</div>
-<div class="sect3">
-<h4 id="_connector">3.4.4. connector</h4>
-<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
-<div class="paragraph"><p>Operations allowed: <code>CREATE</code>, <code>DELETE</code>, <code>READ</code></p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>addr</em> (string, default=<em>127.0.0.1</em>, <code>CREATE</code>)
-</dt>
-<dd>
-<p>
- (DEPRECATED)IP address: ipv4 or ipv6 literal or a host name. This attribute has been deprecated. Use host instead
<TRUNCATED>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[05/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/book.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/book.html.in b/input/releases/qpid-dispatch-master/book.html.in
index 64014d3..bb2aa8e 100644
--- a/input/releases/qpid-dispatch-master/book.html.in
+++ b/input/releases/qpid-dispatch-master/book.html.in
@@ -1,759 +1,17 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>Qpid Dispatch Router Book</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install(2);
-/*]]>*/
-</script>
-</head>
-<body class="book">
-<div id="header">
-<h1>Qpid Dispatch Router Book</h1>
-<div id="toc">
- <div id="toctitle">Table of Contents</div>
- <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="introduction">1. Introduction</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="overview">1.1. Overview</h3>
-<div class="paragraph"><p>The Dispatch router is an AMQP message router that provides
+<hr>
+<h2><a name="introduction"></a>1. Introduction</h2>
+<h3><a name="overview"></a>1.1. Overview</h3>
+<p>The Dispatch router is an AMQP message router that provides
advanced interconnect capabilities. It allows flexible routing of
messages between any AMQP-enabled endpoints, whether they be clients,
servers, brokers or any other entity that can send or receive standard
-AMQP messages.</p></div>
-<div class="paragraph"><p>A messaging client can make a single AMQP connection into a messaging
+AMQP messages.</p>
+<p>A messaging client can make a single AMQP connection into a messaging
bus built of Dispatch routers and, over that connection, exchange
messages with one or more message brokers, and at the same time exchange
messages directly with other endpoints without involving a broker at
-all.</p></div>
-<div class="paragraph"><p>The router is an intermediary for messages but it is <em>not</em> a broker. It
+all.</p>
+<p>The router is an intermediary for messages but it is <em>not</em> a broker. It
does not <em>take responsibility for</em> messages. It will, however, propagate
settlement and disposition across a network such that delivery
guarantees are met. In other words: the router network will deliver the
@@ -763,14 +21,14 @@ the same path. This means that <em>responsibility</em> for the message is
transfered from the original sender to the ultimate receiver <em>as if
they were directly connected</em>. However this is done via a flexible
network that allows highly configurable routing of the message
-transparent to both sender and receiver.</p></div>
-<div class="paragraph"><p>There are some patterns where this enables "brokerless messaging"
+transparent to both sender and receiver.</p>
+<p>There are some patterns where this enables "brokerless messaging"
approaches that are preferable to brokered approaches. In other cases a
broker is essential (in particular where you need the separation of
responsibility and/or the buffering provided by store-and-forward) but a
dispatch network can still be useful to tie brokers and clients together
-into patterns that are difficult with a single broker.</p></div>
-<div class="paragraph"><p>For a "brokerless" example, consider the common brokered implementation
+into patterns that are difficult with a single broker.</p>
+<p>For a "brokerless" example, consider the common brokered implementation
of the request-response pattern, a client puts a request on a queue and
then waits for a reply on another queue. In this case the broker can be
a hindrance - the client may want to know immediatly if there is nobody
@@ -779,8 +37,8 @@ discover this. With a dispatch network, the client can be informed
immediately if its message cannot be delivered because nobody is
listening. When the client receives acknowledgement of the request it
knows not just that it is sitting on a queue, but that it has actually
-been received by the server.</p></div>
-<div class="paragraph"><p>For an exampe of using dispatch to enhance the use of brokers, consider
+been received by the server.</p>
+<p>For an exampe of using dispatch to enhance the use of brokers, consider
using an array of brokers to implement a scalable distributed work
queue. A dispatch network can make this appear as a single queue, with
senders publishing to a single address and receivers subscribing to a
@@ -792,8 +50,8 @@ pattern with brokers alone. If a receiver is connected to a broker that
has no messages, but there are messages on another broker, you have to
somehow transfer them or leave them "stuck". With a dispatch network,
<em>all</em> the receivers are connected to <em>all</em> the brokers. If there is a
-message anywhere it can be delivered to any receiver.</p></div>
-<div class="paragraph"><p>The router is meant to be deployed in topologies of multiple routers,
+message anywhere it can be delivered to any receiver.</p>
+<p>The router is meant to be deployed in topologies of multiple routers,
preferably with redundant paths. It uses link-state routing protocols
and algorithms (similar to OSPF or IS-IS from the networking world) to
calculate the best path from every point to every other point and to
@@ -803,12 +61,10 @@ continued connectivity in the face of system or network failure. Because
it never takes responsibility for messages it is effectively stateless.
Messages not delivered to their final destination will not be
acknowledged to the sender and therefore the sender can re-send such
-messages if it is disconnected from the network.</p></div>
-</div>
-<div class="sect2">
-<h3 id="benefits">1.2. Benefits</h3>
-<div class="paragraph"><p>Simplifies connectivity</p></div>
-<div class="ulist"><ul>
+messages if it is disconnected from the network.</p>
+<h3><a name="benefits"></a>1.2. Benefits</h3>
+<p>Simplifies connectivity</p>
+<ul>
<li>
<p>
An endpoint can do all of its messaging through a single transport
@@ -820,9 +76,9 @@ connection
Avoid opening holes in firewalls for incoming connections
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>Provides messaging connectivity where there is no TCP/IP connectivity</p></div>
-<div class="ulist"><ul>
+</ul>
+<p>Provides messaging connectivity where there is no TCP/IP connectivity</p>
+<ul>
<li>
<p>
A server or broker can be in a private IP network (behind a NAT
@@ -830,9 +86,9 @@ firewall) and be accessible by messaging endpoints in other networks
(learn more).
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>Simplifies reliability</p></div>
-<div class="ulist"><ul>
+</ul>
+<p>Simplifies reliability</p>
+<ul>
<li>
<p>
Reliability and availability are provided using redundant topology,
@@ -849,29 +105,27 @@ Reliable end-to-end messaging without persistent stores
Use a message broker only when you need store-and-forward semantics
</p>
</li>
-</ul></div>
-</div>
-<div class="sect2">
-<h3 id="features">1.3. Features</h3>
-<div class="ulist"><ul>
+</ul>
+<h3><a name="features"></a>1.3. Features</h3>
+<ul>
<li>
<p>
Can be deployed stand-alone or in a network of routers
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Supports arbitrary network topology - no restrictions on redundancy
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Automatic route computation - adjusts quickly to changes in topology
</p>
</li>
-</ul></div>
+</ul>
</li>
-</ul></div>
+</ul>
</li>
<li>
<p>
@@ -883,50 +137,40 @@ Provides remote access to brokers or other AMQP servers
Security
</p>
</li>
-</ul></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="using-qpid-dispatch">2. Using Qpid Dispatch</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="configuration">2.1. Configuration</h3>
-<div class="paragraph"><p>The default configuration file is installed in
-<em>install-prefix/etc/qpid-dispatch/qdrouterd.conf</em>. This configuration file will
+</ul>
+<hr>
+<h2><a name="using-qpid-dispatch"></a>2. Using Qpid Dispatch</h2>
+<h3><a name="configuration"></a>2.1. Configuration</h3>
+<p>The default configuration file is installed in
+<em>/usr/local/etc/qpid-dispatch/qdrouterd.conf</em>. 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></div>
-<div class="paragraph"><p>To run the router, invoke the executable: qdrouterd [-c my-config-file]</p></div>
-<div class="paragraph"><p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
-page.</p></div>
-</div>
-<div class="sect2">
-<h3 id="tools">2.2. Tools</h3>
-<div class="sect3">
-<h4 id="qdstat">2.2.1. qdstat</h4>
-<div class="paragraph"><p><em>qdstat</em> is a command line tool that lets you view the status of a
+configuration to load.</p>
+<p>To run the router, invoke the executable: <code>qdrouterd [-c my-config-file]</code></p>
+<p>For more details of the configuration file see the <em>qdrouterd.conf(5)</em> man
+page.</p>
+<h3><a name="tools"></a>2.2. Tools</h3>
+<h4><a name="qdstat"></a>2.2.1. qdstat</h4>
+<p><em>qdstat</em> is a command line tool that lets you view the status of a
Dispatch Router. The following options are useful for seeing what the
-router is doing:</p></div>
-<div class="tableblock">
+router is doing:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="17%" />
-<col width="83%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Option</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="17%" valign="top"><em>Option</em> </th>
+<th align="left" width="83%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">-l</p></td>
-<td align="left" valign="top"><p class="table">Print a list of AMQP links attached to the router. Links are
+<td align="left" width="17%" valign="top"><p>-l</p></td>
+<td align="left" width="83%" valign="top"><p>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
@@ -934,76 +178,65 @@ router. Router links are attached to other routers in a network of
routbers.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-a</p></td>
-<td align="left" valign="top"><p class="table">Print a list of addresses known to the router.</p></td>
+<td align="left" width="17%" valign="top"><p>-a</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of addresses known to the router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-n</p></td>
-<td align="left" valign="top"><p class="table">Print a list of known routers in the network.</p></td>
+<td align="left" width="17%" valign="top"><p>-n</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of known routers in the network.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">-c</p></td>
-<td align="left" valign="top"><p class="table">Print a list of connections to the router.</p></td>
+<td align="left" width="17%" valign="top"><p>-c</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of connections to the router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">--autolinks</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configured auto-links.</p></td>
+<td align="left" width="17%" valign="top"><p>--autolinks</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of configured auto-links.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">--linkroutes</p></td>
-<td align="left" valign="top"><p class="table">Print a list of configures link-routes.</p></td>
+<td align="left" width="17%" valign="top"><p>--linkroutes</p></td>
+<td align="left" width="83%" valign="top"><p>Print a list of configures link-routes.</p></td>
</tr>
</tbody>
</table>
</div>
-<div class="paragraph"><p>For complete details see the <em>qdstat(8)</em> man page and the output of
-<code>qdstat --help</code>.</p></div>
-</div>
-<div class="sect3">
-<h4 id="qdmanage">2.2.2. qdmanage</h4>
-<div class="paragraph"><p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
+<p>For complete details see the <em>qdstat(8)</em> man page and the output of
+<code>qdstat --help</code>.</p>
+<h4><a name="qdmanage"></a>2.2.2. qdmanage</h4>
+<p><em>qdmanage</em> is a general-purpose AMQP management client that allows you
to not only view but modify the configuration of a running dispatch
-router.</p></div>
-<div class="paragraph"><p>For example you can query all the connection entities in the router:</p></div>
-<div class="listingblock">
-<div class="content">
+router.</p>
+<p>For example you can query all the connection entities in the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage query --type connection</code></pre>
-</div></div>
-<div class="paragraph"><p>To enable logging debug and higher level messages by default:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>To enable logging debug and higher level messages by default:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage update log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="paragraph"><p>In fact, everything that can be configured in the configuration file can
+</td></tr></table>
+<p>In fact, everything that can be configured in the configuration file can
also be created in a running router via management. For example to
-create a new listener in a running router:</p></div>
-<div class="listingblock">
-<div class="content">
+create a new listener in a running router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage create type=listener port=5555</code></pre>
-</div></div>
-<div class="paragraph"><p>Now you can connect to port 5555, for exampple:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>Now you can connect to port 5555, for exampple:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdmanage query -b localhost:5555 --type listener</code></pre>
-</div></div>
-<div class="paragraph"><p>For complete details see the <em>qdmanage(8)</em> man page and the output of
+</td></tr></table>
+<p>For complete details see the <em>qdmanage(8)</em> man page and the output of
<code>qdmanage --help</code>. Also for details of what can be configured see the
-<em>qdrouterd.conf(5)</em> man page.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="basic-usage-and-examples">2.3. Basic Usage and Examples</h3>
-<div class="sect3">
-<h4 id="standalone-and-interior-modes">2.3.1. Standalone and Interior Modes</h4>
-<div class="paragraph"><p>The router can operate stand-alone or as a node in a network of routers.
+<em>qdrouterd.conf(5)</em> man page.</p>
+<h3><a name="basic-usage-and-examples"></a>2.3. Basic Usage and Examples</h3>
+<h4><a name="standalone-and-interior-modes"></a>2.3.1. Standalone and Interior Modes</h4>
+<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></div>
-<div class="paragraph"><p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
-like the following:</p></div>
-<div class="listingblock">
-<div class="content">
+endpoints.</p>
+<p>If your router is running in stand-alone mode, <em>qdstat -a</em> will look
+like the following:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1013,16 +246,15 @@ Router Addresses
mobile $management 0 closest 1 0 0 0 1 0 0 1 0
local $management closest 1 0 0 0 0 0 0 0 0
local temp.1GThUllfR7N+BDP closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that there are a number of known addresses. <em>$management</em> is the
+</td></tr></table>
+<p>Note that there are a number of known addresses. <em>$management</em> is the
address of the router’s embedded management agent.
<em>temp.1GThUllfR7N+BDP</em> is the temporary reply-to address of the <em>qdstat</em>
-client making requests to the agent.</p></div>
-<div class="paragraph"><p>If you change the mode to interior and restart the processs, the same
+client making requests to the agent.</p>
+<p>If you change the mode to interior and restart the processs, the same
command will yield additional addresses which are used for inter-router
-communication:</p></div>
-<div class="listingblock">
-<div class="content">
+communication:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1037,25 +269,21 @@ Router Addresses
local qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
topo qdrouter.ma multicast 1 0 0 0 0 0 0 0 0
local temp.wfx54+zf+YWQF3T closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="mobile-subscribers">2.3.2. Mobile Subscribers</h4>
-<div class="paragraph"><p>The term "mobile subscriber" simply refers to the fact that a client may
+</td></tr></table>
+<h4><a name="mobile-subscribers"></a>2.3.2. Mobile Subscribers</h4>
+<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></div>
-<div class="paragraph"><p>To illustrate a subscription on a stand-alone router, you can use the
+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>simple_recv.py</em>
-example receiver:</p></div>
-<div class="listingblock">
-<div class="content">
+example receiver:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python ./simple_recv.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-<div class="paragraph"><p>This command creates a receiving link subscribed to the specified
-address. To verify the subscription:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>This command creates a receiving link subscribed to the specified
+address. To verify the subscription:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
@@ -1066,24 +294,20 @@ Router Addresses
local $management closest 1 0 0 0 0 0 0 0 0
mobile my-address 0 closest 0 1 0 0 0 0 0 0 0
local temp.75_d2X23x_KOT51 closest 0 1 0 0 0 0 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>You can then, in a separate command window, run a sender to produce
-messages to that address:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>You can then, in a separate command window, run a sender to produce
+messages to that address:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python ./simple_send.py -a 127.0.0.1/my-address</code></pre>
-</div></div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-reply-to">2.3.3. Dynamic Reply-To</h4>
-<div class="paragraph"><p>Dynamic reply-to can be used to obtain a reply-to address that routes
+</td></tr></table>
+<h4><a name="dynamic-reply-to"></a>2.3.3. Dynamic Reply-To</h4>
+<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></div>
-<div class="listingblock">
-<div class="content">
+routers' management addresses.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>#include <qpid/messaging/Address.h>
#include <qpid/messaging/Connection.h>
#include <qpid/messaging/Message.h>
@@ -1124,11 +348,10 @@ int main() {
connection.close();
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The equivalent program written in Python against the Proton Messenger
-API:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>The equivalent program written in Python against the Proton Messenger
+API:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>from proton import Messenger, Message
def main():
@@ -1159,14 +382,11 @@ def main():
messenger.stop()
main()</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="link-routing">2.4. Link Routing</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.4. This feature was
-significantly updated in Qpid Dispatch 0.6.</p></div>
-<div class="paragraph"><p>Link-routing is an alternative strategy for routing messages across a
+</td></tr></table>
+<h3><a name="link-routing"></a>2.4. Link Routing</h3>
+<p>This feature was introduced in Qpid Dispatch 0.4. This feature was
+significantly updated in Qpid Dispatch 0.6.</p>
+<p>Link-routing is an alternative strategy for routing messages across a
network of routers. With the existing message-routing strategy, each
router makes a routing decision on a per-message basis when the message
is delivered. Link-routing is different because it makes routing
@@ -1174,18 +394,17 @@ decisions when link-attach frames arrive. A link is effectively chained
across the network of routers from the establishing node to the
destination node. Once the link is established, the transfer of message
deliveries, flow frames, and dispositions is performed across the routed
-link.</p></div>
-<div class="paragraph"><p>The main benefit to link-routing is that endpoints can use the full link
+link.</p>
+<p>The main benefit to link-routing is that endpoints can use the full link
protocol to interact with other endpoints in far-flung parts of the
network. For example, a client can establish a receiver across the
network to a queue on a remote broker and use link credit to control
the flow of messages from the broker. Similarly, a receiver can
establish a link to a topic on a remote broker using a server-side
-filter.</p></div>
-<div class="paragraph"><p>Why would one want to do this? One reason is to provide client
-isolation. A network like the following can be deployed:</p></div>
-<div class="listingblock">
-<div class="content">
+filter.</p>
+<p>Why would one want to do this? One reason is to provide client
+isolation. A network like the following can be deployed:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code> Public Network
+-----------------+
| +-----+ |
@@ -1205,29 +424,27 @@ isolation. A network like the following can be deployed:</p></div>
| | | |
| | | |
+-----------------+ +-----------------+</code></pre>
-</div></div>
-<div class="paragraph"><p>The clients in Private Net B can be constrained (by firewall policy)
+</td></tr></table>
+<p>The clients in Private Net B can be constrained (by firewall policy)
to only connect to the Router in their own network. Using
link-routing, these clients can access queues, topics, and other AMQP
-services that are in the Public Network or even in Private Net A.</p></div>
-<div class="paragraph"><p>For example, The router Ra can be configured to expose queues in
+services that are in the Public Network or even in Private Net A.</p>
+<p>For example, The router Ra can be configured to expose queues in
broker B2 to the network. Client C1 can then establish a connection
to Rb, the local router, open a subscribing link to "b2.event-queue",
-and receive messages stored on that queue in broker B2.</p></div>
-<div class="paragraph"><p>C1 is unable to create a TCP/IP connection to B1 because of its
+and receive messages stored on that queue in broker B2.</p>
+<p>C1 is unable to create a TCP/IP connection to B1 because of its
isolation (and because B2 is itself in a private network). However, with
-link routing, C1 can interact with B2 using the AMQP link protocol.</p></div>
-<div class="paragraph"><p>Note that in this case, neither C1 nor B2 have been modified in any way
+link routing, C1 can interact with B2 using the AMQP link protocol.</p>
+<p>Note that in this case, neither C1 nor B2 have been modified in any way
and neither need be aware of the fact that there is a message-router
-network between them.</p></div>
-<div class="sect3">
-<h4 id="link-routing-configuration">2.4.1. Configuration</h4>
-<div class="paragraph"><p>Starting with the configured topology shown above, how is link-routing
-configured to support the example described above?</p></div>
-<div class="paragraph"><p>First, router Ra needs to be told how to make a connection to the broker
-B2:</p></div>
-<div class="listingblock">
-<div class="content">
+network between them.</p>
+<h4><a name="link-routing-configuration"></a>2.4.1. Configuration</h4>
+<p>Starting with the configured topology shown above, how is link-routing
+configured to support the example described above?</p>
+<p>First, router Ra needs to be told how to make a connection to the broker
+B2:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker
role: route-container
@@ -1235,13 +452,12 @@ B2:</p></div>
port: <B2-port>
saslMechanisms: ANONYMOUS
}</code></pre>
-</div></div>
-<div class="paragraph"><p>This <em>route-container</em> connector tells the router how to connect to an
+</td></tr></table>
+<p>This <em>route-container</em> connector tells the router how to connect to an
external AMQP container when it is needed. The name "broker" will be
-used later to refer to this connection.</p></div>
-<div class="paragraph"><p>Now, the router must be configured to route certain addresses to B2:</p></div>
-<div class="listingblock">
-<div class="content">
+used later to refer to this connection.</p>
+<p>Now, the router must be configured to route certain addresses to B2:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>linkRoute {
prefix: b2
dir: in
@@ -1253,18 +469,18 @@ linkRoute {
dir: out
connection: broker
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The linkRoute tells router Ra that any sender or receiver that is
+</td></tr></table>
+<p>The linkRoute tells router Ra that any sender or receiver that is
attached with a target or source (respectively) whos address begins with
"b2", should be routed to the broker B2 (via the route-container
-connector).</p></div>
-<div class="paragraph"><p>Note that receiving and sending links are configured and routed
+connector).</p>
+<p>Note that receiving and sending links are configured and routed
separately. This allows configuration of link routes for listeners only
or senders only. A direction of "in" matches client senders (i.e. links
that carry messages inbound to the router network). Direction "out"
-matches client receivers.</p></div>
-<div class="paragraph"><p>Examples of addresses that "begin with <em>b2</em>" include:</p></div>
-<div class="ulist"><ul>
+matches client receivers.</p>
+<p>Examples of addresses that "begin with <em>b2</em>" include:</p>
+<ul>
<li>
<p>
b2
@@ -1280,44 +496,40 @@ b2.queues
b2.queues.app1
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>When the route-container connector is configured, router Ra establishes
+</ul>
+<p>When the route-container connector is configured, router Ra establishes
a connection to the broker. Once the connection is open, Ra tells the
other routers (Rp and Rb) that it is a valid destination for link-routes
to the "b2" prefix. This means that sender or receiver links attached to
Rb or Rp will be routed via the shortest path to Ra where they are then
-routed outbound to the broker B2.</p></div>
-<div class="paragraph"><p>On Rp and Rb, it is advisable to add the identical configuration. It is
+routed outbound to the broker B2.</p>
+<p>On Rp and Rb, it is advisable to add the identical configuration. It is
permissible for a linkRoute configuration to reference a connection that
-does not exist.</p></div>
-<div class="paragraph"><p>This configuration tells the routers that link-routing is intended to be
+does not exist.</p>
+<p>This configuration tells the routers that link-routing is intended to be
available for targets and sources starting with "b2". This is important
because it is possible that B2 might be unavailable or shut off. If B2
is unreachable, Ra will not advertize itself as a destination for "b2"
and the other routers might never know that "b2" was intended for
-link-routing.</p></div>
-<div class="paragraph"><p>The above configuration allows Rb and Rp to reject attaches that should
+link-routing.</p>
+<p>The above configuration allows Rb and Rp to reject attaches that should
be routed to B2 with an error message that indicates that there is no
-route available to the destination.</p></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="indirect-waypoints-and-auto-links">2.5. Indirect Waypoints and Auto-Links</h3>
-<div class="paragraph"><p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
+route available to the destination.</p>
+<h3><a name="indirect-waypoints-and-auto-links"></a>2.5. Indirect Waypoints and Auto-Links</h3>
+<p>This feature was introduced in Qpid Dispatch 0.6. It is a significant
improvement on an earlier somewhat experimental feature called
-Waypoints.</p></div>
-<div class="paragraph"><p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
+Waypoints.</p>
+<p>Auto-link is a feature of Qpid Dispatch Router that enables a router to
actively attach a link to a node on an external AMQP container. The
obvious application for this feature is to route messages through a
-queue on a broker, but other applications are possible as well.</p></div>
-<div class="paragraph"><p>An auto-link manages the lifecycle of one AMQP link. If messages are to
+queue on a broker, but other applications are possible as well.</p>
+<p>An auto-link manages the lifecycle of one AMQP link. If messages are to
be routed to and from a queue on a broker, then two auto-links are
needed: one for sending messages to the queue and another for receiving
messages from the queue. The container to which an auto-link attempts to
-attach may be identified in one of two ways:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="ulist"><ul>
+attach may be identified in one of two ways:</p>
+<blockquote>
+<ul>
<li>
<p>
The name of the connector/listener that resulted in the connection of
@@ -1329,16 +541,14 @@ the container, or
The AMQP container-id of the remote container.
</p>
</li>
-</ul></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="sect3">
-<h4 id="queue-waypoint-example">2.5.1. Queue Waypoint Example</h4>
-<div class="paragraph"><p>Here is an example configuration for routing messages deliveries through
-a pair of queues on a broker:</p></div>
-<div class="listingblock">
-<div class="content">
+</ul>
+<p align="right">
+</p>
+</blockquote>
+<h4><a name="queue-waypoint-example"></a>2.5.1. Queue Waypoint Example</h4>
+<p>Here is an example configuration for routing messages deliveries through
+a pair of queues on a broker:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker
role: route-container
@@ -1375,15 +585,14 @@ autoLink {
dir: out
connection: broker
}</code></pre>
-</div></div>
-<div class="paragraph"><p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
+</td></tr></table>
+<p>The <code>address</code> entity identifies a namespace <em>queue.</em> that will be used
for routing messages through queues via autolinks. The four <code>autoLink</code> entities
identify the head and tail of two queues on the broker that will be connected
-via auto-links.</p></div>
-<div class="paragraph"><p>If there is no broker connected, the auto-links shall remain
-<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p></div>
-<div class="listingblock">
-<div class="content">
+via auto-links.</p>
+<p>If there is no broker connected, the auto-links shall remain
+<em>inactive</em>. This can be observed by using the <code>qdstat</code> tool:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat --autolinks
AutoLinks
addr dir phase link status lastErr
@@ -1392,11 +601,10 @@ AutoLinks
queue.first out 0 inactive
queue.second in 1 inactive
queue.second out 0 inactive</code></pre>
-</div></div>
-<div class="paragraph"><p>If a broker comes online with a queue called <em>queue.first</em>, the
-auto-links will attempt to activate:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>If a broker comes online with a queue called <em>queue.first</em>, the
+auto-links will attempt to activate:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat --autolinks
AutoLinks
addr dir phase link status lastErr
@@ -1405,67 +613,60 @@ AutoLinks
queue.first out 0 7 active
queue.second in 1 failed Node not found: queue.second
queue.second out 0 failed Node not found: queue.second</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that two of the auto-links are in <em>failed</em> state because the queue
-does not exist on the broker.</p></div>
-<div class="paragraph"><p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
-three messages to <em>queue.first</em> via the router:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>Note that two of the auto-links are in <em>failed</em> state because the queue
+does not exist on the broker.</p>
+<p>If we now use the Qpid Proton example application <code>simple_send.py</code> to send
+three messages to <em>queue.first</em> via the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python simple_send.py -a 127.0.0.1/queue.first -m3
all messages confirmed</code></pre>
-</div></div>
-<div class="paragraph"><p>and then look at the address statistics on the router:</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>and then look at the address statistics on the router:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
========================================================================================================
mobile queue.first 1 balanced 0 0 0 0 0 0 0 0 0
mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>we see that <em>queue.first</em> appears twice in the list of addresses. The
+</td></tr></table>
+<p>we see that <em>queue.first</em> appears twice in the list of addresses. The
<code>phs</code>, or phase column shows that there are two phases for the
address. Phase <em>0</em> is for routing message deliveries from producers to
the tail of the queue (the <code>out</code> auto-link associated with the queue).
Phase 1 is for routing deliveries from the head of the queue to
-subscribed consumers.</p></div>
-<div class="paragraph"><p>Note that three deliveries have been counted in the "in" and "out"
+subscribed consumers.</p>
+<p>Note that three deliveries have been counted in the "in" and "out"
columns for phase <em>0</em>. The "in" column represents the three messages
that arrived from <code>simple_send.py</code> and the <code>out</code> column represents the three
-deliveries to the queue on the broker.</p></div>
-<div class="paragraph"><p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p></div>
-<div class="listingblock">
-<div class="content">
+deliveries to the queue on the broker.</p>
+<p>If we now use <code>simple_recv.py</code> to receive three messages from this address:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ python simple_recv.py -a 127.0.0.1:5672/queue.first -m3
{u'sequence': int32(1)}
{u'sequence': int32(2)}
{u'sequence': int32(3)}</code></pre>
-</div></div>
-<div class="paragraph"><p>We receive the three queued messages. Looking at the addresses again, we
+</td></tr></table>
+<p>We receive the three queued messages. Looking at the addresses again, we
see that phase 1 was used to deliver those messages from the queue to
-the consumer.</p></div>
-<div class="listingblock">
-<div class="content">
+the consumer.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>$ qdstat -a
Router Addresses
class addr phs distrib in-proc local remote cntnr in out thru to-proc from-proc
========================================================================================================
mobile queue.first 1 balanced 0 0 0 0 3 3 0 0 0
mobile queue.first 0 balanced 0 1 0 0 3 3 0 0 0</code></pre>
-</div></div>
-<div class="paragraph"><p>Note that even in a multi-router network, and with multiple producers
+</td></tr></table>
+<p>Note that even in a multi-router network, and with multiple producers
and consumers for <em>queue.first</em>, all deliveries will be routed through
-the queue on the connected broker.</p></div>
-</div>
-<div class="sect3">
-<h4 id="sharded-queue-example">2.5.2. Sharded Queue Example</h4>
-<div class="paragraph"><p>Here is an extension of the above example to illustrate how Qpid
+the queue on the connected broker.</p>
+<h4><a name="sharded-queue-example"></a>2.5.2. Sharded Queue Example</h4>
+<p>Here is an extension of the above example to illustrate how Qpid
Dispatch Router can be used to create a distributed queue in which
-multiple brokers share the message-queueing load.</p></div>
-<div class="listingblock">
-<div class="content">
+multiple brokers share the message-queueing load.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
name: broker1
role: route-container
@@ -1510,79 +711,66 @@ autoLink {
dir: out
connection: broker2
}</code></pre>
-</div></div>
-<div class="paragraph"><p>In the above configuration, there are two instances of <em>queue.first</em> on
+</td></tr></table>
+<p>In the above configuration, there are two instances of <em>queue.first</em> on
brokers 1 and 2. Message traffic from producers to address <em>queue.first</em>
shall be balanced between the two instance and messages from the queues
shall be balanced across the collection of subscribers to the same
-address.</p></div>
-</div>
-<div class="sect3">
-<h4 id="dynamically-adding-shards">2.5.3. Dynamically Adding Shards</h4>
-<div class="paragraph"><p>Since configurable entities in the router can also be accessed via the
+address.</p>
+<h4><a name="dynamically-adding-shards"></a>2.5.3. Dynamically Adding Shards</h4>
+<p>Since configurable entities in the router can also be accessed via the
management protocol, we can remotely add a shard to the above example
-using <code>qdmanage</code>:</p></div>
-<div class="listingblock">
-<div class="content">
+using <code>qdmanage</code>:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>qdmanage create --type org.apache.qpid.dispatch.connector host=<host> port=<port> name=broker3
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=in connection=broker3
qdmanage create --type org.apache.qpid.dispatch.router.config.autoLink addr=queue.first dir=out connection=broker3</code></pre>
-</div></div>
-</div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="technical-details-and-specifications">3. Technical Details and Specifications</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="client-compatibility">3.1. Client Compatibility</h3>
-<div class="paragraph"><p>Dispatch Router should, in theory, work with any client that is
-compatible with AMQP 1.0. The following clients have been tested:</p></div>
-<div class="tableblock">
+</td></tr></table>
+<hr>
+<h2><a name="technical-details-and-specifications"></a>3. Technical Details and Specifications</h2>
+<h3><a name="client-compatibility"></a>3.1. Client Compatibility</h3>
+<p>Dispatch Router should, in theory, work with any client that is
+compatible with AMQP 1.0. The following clients have been tested:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="22%" />
-<col width="78%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Client</em> </th>
-<th align="left" valign="top"><em>Notes</em></th>
+<th align="left" width="22%" valign="top"><em>Client</em> </th>
+<th align="left" width="78%" valign="top"><em>Notes</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">qpid::messaging</p></td>
-<td align="left" valign="top"><p class="table">The Qpid messaging clients work with Dispatch Router
+<td align="left" width="22%" valign="top"><p>qpid::messaging</p></td>
+<td align="left" width="78%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">Proton Reactor</p></td>
-<td align="left" valign="top"><p class="table">The Proton Reactor API is compatible with Dispatch
+<td align="left" width="22%" valign="top"><p>Proton Reactor</p></td>
+<td align="left" width="78%" valign="top"><p>The Proton Reactor API is compatible with Dispatch
Router.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">Proton Messenger</p></td>
-<td align="left" valign="top"><p class="table">Messenger works with Dispatch Router.</p></td>
+<td align="left" width="22%" valign="top"><p>Proton Messenger</p></td>
+<td align="left" width="78%" valign="top"><p>Messenger works with Dispatch Router.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-<div class="sect2">
-<h3 id="addressing">3.2. Addressing</h3>
-<div class="paragraph"><p>AMQP addresses are used to control the flow of messages across a network
+<h3><a name="addressing"></a>3.2. Addressing</h3>
+<p>AMQP addresses are used to control the flow of messages across a network
of routers. Addresses are used in a number of different places in the
AMQP 1.0 protocol. They can be used in a specific message in the <code>to</code>
and <code>reply-to</code> fields of a message’s properties. They are also used
during the creation of links in the <code>address</code> field of a <code>source</code> or
-a <code>target</code>.</p></div>
-<div class="paragraph"><p>Addresses designate various kinds of entities in a messaging network:</p></div>
-<div class="ulist"><ul>
+a <code>target</code>.</p>
+<p>Addresses designate various kinds of entities in a messaging network:</p>
+<ul>
<li>
<p>
Endpoint processes that consume data or offer a service
@@ -1597,7 +785,7 @@ Topics that match multiple consumers to multiple producers
<p>
Entities within a messaging broker:
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
Queues
@@ -1613,23 +801,23 @@ Durable Topics
Exchanges
</p>
</li>
-</ul></div>
+</ul>
</li>
-</ul></div>
-<div class="paragraph"><p>The syntax of an AMQP address is opaque as far as the router network is
+</ul>
+<p>The syntax of an AMQP address is opaque as far as the router network is
concerned. A syntactical structure may be used by the administrator that
creates addresses, but the router treats them as opaque strings. Routers
consider addresses to be mobile such that any address may be directly
connected to any router in a network and may move around the topology.
In cases where messages are broadcast to or balanced across multiple
consumers, an address may be connected to multiple routers in the
-network.</p></div>
-<div class="paragraph"><p>Addresses have semantics associated with them. When an address is
+network.</p>
+<p>Addresses have semantics associated with them. When an address is
created in the network, it is assigned a set of semantics (and access
rules) during a process called provisioning. The semantics of an address
-control how routers behave when they see the address being used.</p></div>
-<div class="paragraph"><p>Address semantics include the following considerations:</p></div>
-<div class="ulist"><ul>
+control how routers behave when they see the address being used.</p>
+<p>Address semantics include the following considerations:</p>
+<ul>
<li>
<p>
<em>Routing pattern</em> - direct, multicast, balanced
@@ -1645,40 +833,37 @@ control how routers behave when they see the address being used.</p></div>
<em>Reliability</em> - N destinations, etc.
</p>
</li>
-</ul></div>
-<div class="sect3">
-<h4 id="routing-patterns">3.2.1. Routing patterns</h4>
-<div class="paragraph"><p>Routing patterns constrain the paths that a message can take across a
-network.</p></div>
-<div class="tableblock">
+</ul>
+<h4><a name="routing-patterns"></a>3.2.1. Routing patterns</h4>
+<p>Routing patterns constrain the paths that a message can take across a
+network.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="18%" />
-<col width="82%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="18%" valign="top"><em>Pattern</em> </th>
+<th align="left" width="82%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><em>Direct</em></p></td>
-<td align="left" valign="top"><p class="table">Direct routing allows for only one consumer to use an address
+<td align="left" width="18%" valign="top"><p><em>Direct</em></p></td>
+<td align="left" width="82%" valign="top"><p>Direct routing allows for only one consumer to use an address
at a time. Messages (or links) follow the lowest cost path across the
network from the sender to the one receiver.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>Multicast</em></p></td>
-<td align="left" valign="top"><p class="table">Multicast routing allows multiple consumers to use the
+<td align="left" width="18%" valign="top"><p><em>Multicast</em></p></td>
+<td align="left" width="82%" valign="top"><p>Multicast routing allows multiple consumers to use the
same address at the same time. Messages are routed such that each
consumer receives a copy of the message.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>Balanced</em></p></td>
-<td align="left" valign="top"><p class="table">Balanced routing also allows multiple consumers to use the
+<td align="left" width="18%" valign="top"><p><em>Balanced</em></p></td>
+<td align="left" width="82%" valign="top"><p>Balanced routing also allows multiple consumers to use the
same address. In this case, messages are routed to exactly one of the
consumers, and the network attempts to balance the traffic load across
the set of consumers using the same address.</p></td>
@@ -1686,59 +871,53 @@ the set of consumers using the same address.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="routing-mechanisms">3.2.2. Routing mechanisms</h4>
-<div class="paragraph"><p>The fact that addresses can be used in different ways suggests that
+<h4><a name="routing-mechanisms"></a>3.2.2. Routing mechanisms</h4>
+<p>The fact that addresses can be used in different ways suggests that
message routing can be accomplished in different ways. Before going into
the specifics of the different routing mechanisms, it would be good to
-first define what is meant by the term <em>routing</em>:</p></div>
-<div class="quoteblock">
-<div class="content">
-<div class="paragraph"><p>In a network built of multiple routers connected by connections (i.e.,
+first define what is meant by the term <em>routing</em>:</p>
+<blockquote>
+<p>In a network built of multiple routers connected by connections (i.e.,
nodes and edges in a graph), <em>routing</em> determines which connection to
use to send a message directly to its destination or one step closer to
-its destination.</p></div>
-</div>
-<div class="attribution">
-</div></div>
-<div class="paragraph"><p>Each router serves as the terminus of a collection of incoming and
+its destination.</p>
+<p align="right">
+</p>
+</blockquote>
+<p>Each router serves as the terminus of a collection of incoming and
outgoing links. The links either connect directly to endpoints that
produce and consume messages, or they connect to other routers in the
-network along previously established connections.</p></div>
-<div class="sect4">
-<h5 id="message-routing">Message routing</h5>
-<div class="paragraph"><p>Message routing occurs upon delivery of a message and is done based on
-the address in the message’s <code>to</code> field.</p></div>
-<div class="paragraph"><p>When a delivery arrives on an incoming link, the router extracts the
+network along previously established connections.</p>
+<h5><a name="message-routing"></a>Message routing</h5>
+<p>Message routing occurs upon delivery of a message and is done based on
+the address in the message’s <code>to</code> field.</p>
+<p>When a delivery arrives on an incoming link, the router extracts the
address from the delivered message’s <code>to</code> field and looks the address up
in its routing table. The lookup results in zero or more outgoing links
-onto which the message shall be resent.</p></div>
-<div class="tableblock">
+onto which the message shall be resent.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="20%" />
-<col width="80%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Delivery</em> </th>
-<th align="left" valign="top"><em>Handling</em></th>
+<th align="left" width="20%" valign="top"><em>Delivery</em> </th>
+<th align="left" width="80%" valign="top"><em>Handling</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><em>pre-settled</em></p></td>
-<td align="left" valign="top"><p class="table">If the arriving delivery is pre-settled (i.e., fire and
+<td align="left" width="20%" valign="top"><p><em>pre-settled</em></p></td>
+<td align="left" width="80%" valign="top"><p>If the arriving delivery is pre-settled (i.e., fire and
forget), the incoming delivery shall be settled by the router, and the
outgoing deliveries shall also be pre-settled. In other words, the
pre-settled nature of the message delivery is propagated across the
network to the message’s destination.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><em>unsettled</em></p></td>
-<td align="left" valign="top"><p class="table">Unsettled delivery is also propagated across the network.
+<td align="left" width="20%" valign="top"><p><em>unsettled</em></p></td>
+<td align="left" width="80%" valign="top"><p>Unsettled delivery is also propagated across the network.
Because unsettled delivery records cannot be discarded, the router
tracks the incoming deliveries and keeps the association of the incoming
deliveries to the resulting outgoing deliveries. This kept association
@@ -1749,95 +928,83 @@ message traveled.</p></td>
</tbody>
</table>
</div>
-</div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="amqp-mapping">3.3. AMQP Mapping</h3>
-<div class="paragraph"><p>Dispatch Router is an AMQP router and as such, it provides extensions,
+<h3><a name="amqp-mapping"></a>3.3. AMQP Mapping</h3>
+<p>Dispatch Router is an AMQP router and as such, it provides extensions,
code-points, and semantics for routing over AMQP. This page documents the
-details of Dispatch Router’s use of AMQP.</p></div>
-<div class="sect3">
-<h4 id="message-annotations">3.3.1. Message Annotations</h4>
-<div class="paragraph"><p>The following Message Annotation fields are defined by Dispatch Router:</p></div>
-<div class="tableblock">
+details of Dispatch Router’s use of AMQP.</p>
+<h4><a name="message-annotations"></a>3.3.1. Message Annotations</h4>
+<p>The following Message Annotation fields are defined by Dispatch Router:</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="19%" />
-<col width="58%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Field</em> </th>
-<th align="left" valign="top"><em>Type</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="23%" valign="top"><em>Field</em> </th>
+<th align="left" width="19%" valign="top"><em>Type</em> </th>
+<th align="left" width="58%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.ingress</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">The identity of the ingress router for a
+<td align="left" width="23%" valign="top"><p>x-opt-qd.ingress</p></td>
+<td align="left" width="19%" valign="top"><p>string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.trace</p></td>
-<td align="left" valign="top"><p class="table">list of string</p></td>
-<td align="left" valign="top"><p class="table">The list of routers through which this
+<td align="left" width="23%" valign="top"><p>x-opt-qd.trace</p></td>
+<td align="left" width="19%" valign="top"><p>list of string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.to</p></td>
-<td align="left" valign="top"><p class="table">string</p></td>
-<td align="left" valign="top"><p class="table">To-Override for message-routed messages. If this
+<td align="left" width="23%" valign="top"><p>x-opt-qd.to</p></td>
+<td align="left" width="19%" valign="top"><p>string</p></td>
+<td align="left" width="58%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.phase</p></td>
-<td align="left" valign="top"><p class="table">integer</p></td>
-<td align="left" valign="top"><p class="table">The address-phase, if not zero, for messages
+<td align="left" width="23%" valign="top"><p>x-opt-qd.phase</p></td>
+<td align="left" width="19%" valign="top"><p>integer</p></td>
+<td align="left" width="58%" valign="top"><p>The address-phase, if not zero, for messages
flowing between routers.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="sourcetarget-capabilities">3.3.2. Source/Target Capabilities</h4>
-<div class="paragraph"><p>The following Capability values are used in Sources and Targets.</p></div>
-<div class="tableblock">
+<h4><a name="sourcetarget-capabilities"></a>3.3.2. Source/Target Capabilities</h4>
+<p>The following Capability values are used in Sources and Targets.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="19%" />
-<col width="81%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Capability</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="19%" valign="top"><em>Capability</em> </th>
+<th align="left" width="81%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">qd.router</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that are
+<td align="left" width="19%" valign="top"><p>qd.router</p></td>
+<td align="left" width="81%" valign="top"><p>This capability is added to sources and targets that are
used for inter-router message exchange. This capability denotes a link
used for router-control messages flowing between routers.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table">qd.router-data</p></td>
-<td align="left" valign="top"><p class="table">This capability is added to sources and targets that
+<td align="left" width="19%" valign="top"><p>qd.router-data</p></td>
+<td align="left" width="81%" valign="top"><p>This capability is added to sources and targets that
are used for inter-router message exchange. This capability denotes a
link used for user messages being message-routed across an inter-router
connection.</p></td>
@@ -1845,27 +1012,23 @@ connection.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="dynamic-node-properties">3.3.3. Dynamic-Node-Properties</h4>
-<div class="paragraph"><p>The following dynamic-node-properties are used by Dispatch in Sources.</p></div>
-<div class="tableblock">
+<h4><a name="dynamic-node-properties"></a>3.3.3. Dynamic-Node-Properties</h4>
+<p>The following dynamic-node-properties are used by Dispatch in Sources.</p>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="23%" />
-<col width="77%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Property</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="23%" valign="top"><em>Property</em> </th>
+<th align="left" width="77%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table">x-opt-qd.address</p></td>
-<td align="left" valign="top"><p class="table">The node address describing the destination desired
+<td align="left" width="23%" valign="top"><p>x-opt-qd.address</p></td>
+<td align="left" width="77%" valign="top"><p>The node address describing the destination desired
for a dynamic source. If this is absent, the router will terminate any
dynamic receivers. If this address is present, the router will use the
address to route the dynamic link attach to the proper destination
@@ -1874,48 +1037,43 @@ container.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect3">
-<h4 id="addresses-and-address-formats">3.3.4. Addresses and Address Formats</h4>
-<div class="paragraph"><p>The following AMQP addresses and address patterns are used within
-Dispatch Router.</p></div>
-<div class="sect4">
-<h5 id="address-patterns">Address Patterns</h5>
-<div class="tableblock">
+<h4><a name="addresses-and-address-formats"></a>3.3.4. Addresses and Address Formats</h4>
+<p>The following AMQP addresses and address patterns are used within
+Dispatch Router.</p>
+<h5><a name="address-patterns"></a>Address Patterns</h5>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="38%" />
-<col width="62%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Pattern</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="38%" valign="top"><em>Pattern</em> </th>
+<th align="left" width="62%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">An address that references a locally attached endpoint.
+<td align="left" width="38%" valign="top"><p><code>_local/<addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>An address that references a locally attached endpoint.
Messages using this address pattern shall not be routed over more than
one link.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/<router>/<addr></code></p></td>
-<td align="left" valign="top"><p class="table">An address that references an endpoint attached to a specific router
+<td align="left" width="38%" valign="top"><p><code>_topo/0/<router>/<addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>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.</p>
-<p class="table">The <em>0</em> component immediately preceding the router-id is a placeholder
+<p>The <em>0</em> component immediately preceding the router-id is a placeholder
for an <em>area</em> which may be used in the future if area routing is
implemented.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code><addr></code></p></td>
-<td align="left" valign="top"><p class="table">A mobile address. An address of this format represents an
+<td align="left" width="38%" valign="top"><p><code><addr></code></p></td>
+<td align="left" width="62%" valign="top"><p>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
@@ -1924,66 +1082,59 @@ addresses.</p></td>
</tbody>
</table>
</div>
-</div>
-<div class="sect4">
-<h5 id="supported-addresses">Supported Addresses</h5>
-<div class="tableblock">
+<h5><a name="supported-addresses"></a>Supported Addresses</h5>
+<div>
<table rules="all"
width="100%"
frame="border"
cellspacing="0" cellpadding="4">
-<col width="36%" />
-<col width="64%" />
<thead>
<tr>
-<th align="left" valign="top"><em>Address</em> </th>
-<th align="left" valign="top"><em>Description</em></th>
+<th align="left" width="36%" valign="top"><em>Address</em> </th>
+<th align="left" width="64%" valign="top"><em>Description</em></th>
</tr>
</thead>
<tbody>
<tr>
-<td align="left" valign="top"><p class="table"><code>$management</code></p></td>
-<td align="left" valign="top"><p class="table">The management agent on the attached router/container.
+<td align="left" width="36%" valign="top"><p><code>$management</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/$management</code></p></td>
-<td align="left" valign="top"><p class="table">The management agent at Router.E in area
+<td align="left" width="36%" valign="top"><p><code>_topo/0/Router.E/$management</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdhello</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+<td align="left" width="36%" valign="top"><p><code>_local/qdhello</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_local/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity in each of the connected routers.
+<td align="left" width="36%" valign="top"><p><code>_local/qdrouter</code></p></td>
+<td align="left" width="64%" valign="top"><p>The router entity in each of the connected routers.
This address is used by a router to communicate with other routers in
the network.</p></td>
</tr>
<tr>
-<td align="left" valign="top"><p class="table"><code>_topo/0/Router.E/qdrouter</code></p></td>
-<td align="left" valign="top"><p class="table">The router entity at the specifically
+<td align="left" width="36%" valign="top"><p><code>_topo/0/Router.E/qdrouter</code></p></td>
+<td align="left" width="64%" valign="top"><p>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.</p></td>
</tr>
</tbody>
</table>
</div>
-</div>
-</div>
-<div class="sect3">
-<h4 id="implementation-of-the-amqp-management-specification">3.3.5. Implementation of the AMQP Management Specification</h4>
-<div class="paragraph"><p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
-emerging AMQP Management specification (draft 9).</p></div>
-<div class="paragraph"><p>Differences from the specification:</p></div>
-<div class="ulist"><ul>
+<h4><a name="implementation-of-the-amqp-management-specification"></a>3.3.5. Implementation of the AMQP Management Specification</h4>
+<p>Qpid Dispatch is manageable remotely via AMQP. It is compliant with the
+emerging AMQP Management specification (draft 9).</p>
+<p>Differences from the specification:</p>
+<ul>
<li>
<p>
The <code>name</code> attribute is not required when an entity is created. If
@@ -2000,14 +1151,14 @@ The <code>REGISTER</code> and <code>DEREGISTER</code> operations are not impleme
= Management Schema
</p>
</li>
-</ul></div>
-<div class="paragraph"><p>This chapter documents the set of <strong>management entity types</strong> that define
+</ul>
+<p>This chapter documents the set of <strong>management entity types</strong> that define
configuration and management of a Dispatch Router. A management entity type has
a set of <strong>attributes</strong> that can be read, some attributes can also be
-updated. Some entity types also support <strong>operations</strong> that can be called.</p></div>
-<div class="paragraph"><p>All management entity types have the following standard attributes:</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+updated. Some entity types also support <strong>operations</strong> that can be called.</p>
+<p>All management entity types have the following standard attributes:</p>
+<dl>
+<dt>
type
</dt>
<dd>
@@ -2018,7 +1169,7 @@ type
tools will accept the short or long name.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
name
</dt>
<dd>
@@ -2027,7 +1178,7 @@ name
that need to refer to the named entity.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
identity
</dt>
<dd>
@@ -2037,10 +1188,10 @@ identity
<code>listener/localhost:amqp</code>
</p>
</dd>
-</dl></div>
-<div class="paragraph"><p>There are two main categories of management entity type.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<p>There are two main categories of management entity type.</p>
+<dl>
+<dt>
Configuration Entities
</dt>
<dd>
@@ -2050,7 +1201,7 @@ Configuration Entities
tool.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
Operational Entities
</dt>
<dd>
@@ -2058,21 +1209,17 @@ Operational Entities
Run-time status values that can be queried using <code>qdstat(8)</code> or <code>qdmanage(8)</code> tools.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_configuration_entities">3.4. Configuration Entities</h3>
-<div class="paragraph"><p>Configuration entities define the attributes allowed in the configuration file
+</dl>
+<h3><a name="_configuration_entities"></a>3.4. Configuration Entities</h3>
+<p>Configuration entities define the attributes allowed in the configuration file
(see <code>qdrouterd.conf(5)</code>) but you can also create entities once the router is
running using the <code>qdrouterd(8)</code> tool’s <code>c
<TRUNCATED>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/book.pdf
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/book.pdf b/input/releases/qpid-dispatch-master/book.pdf
index dbd7f6e..4896e01 100644
Binary files a/input/releases/qpid-dispatch-master/book.pdf and b/input/releases/qpid-dispatch-master/book.pdf differ
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[07/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/qdstat.8.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/qdstat.8.html b/content/releases/qpid-dispatch-master/qdstat.8.html
index 348f44f..391e4ad 100644
--- a/content/releases/qpid-dispatch-master/qdstat.8.html
+++ b/content/releases/qpid-dispatch-master/qdstat.8.html
@@ -114,818 +114,61 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>NAME</li></ul>
<div id="-middle-content">
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdstat(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdstat(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
+ <h2>NAME</h2>
<p>qdstat -
show status and statistics for a running 'qdrouterd'
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdstat</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Shows status information about networks of Dispatch routers. It can display
-connections, network nodes and links, and router stats such as memory use.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>-g, --general
-: Show General Router Stats</p></div>
-<div class="paragraph"><p>-c, --connections
-: Show Connections</p></div>
-<div class="paragraph"><p>-l, --links
-: Show Router Links</p></div>
-<div class="paragraph"><p>-n, --nodes
-: Show Router Nodes</p></div>
-<div class="paragraph"><p>-a, --address
-: Show Router Addresses</p></div>
-<div class="paragraph"><p>-m, --memory
-: Show Router Memory Stats</p></div>
-<div class="paragraph"><p>--autolinks
-: Show Auto Links</p></div>
-<div class="paragraph"><p>--linkroutes
-: Show Link Routes</p></div>
-<div class="paragraph"><p>-v, --verbose
-: Show maximum detail</p></div>
-<div class="paragraph"><p>--log
-: Show recent log entries</p></div>
-<div class="paragraph"><p>--limit=LIMIT
-: Limit number of log entries</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_output_columns">OUTPUT COLUMNS</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_qdstat_c">qdstat -c</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdstat</strong> [<b>OPTIONS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>Shows status information about networks of Dispatch routers. It can display
+connections, network nodes and links, and router stats such as memory use.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-h, --help
+: show this help message and exit</p>
+<p>--version
+: Print version and exit.</p>
+<p>-g, --general
+: Show General Router Stats</p>
+<p>-c, --connections
+: Show Connections</p>
+<p>-l, --links
+: Show Router Links</p>
+<p>-n, --nodes
+: Show Router Nodes</p>
+<p>-a, --address
+: Show Router Addresses</p>
+<p>-m, --memory
+: Show Router Memory Stats</p>
+<p>--autolinks
+: Show Auto Links</p>
+<p>--linkroutes
+: Show Link Routes</p>
+<p>-v, --verbose
+: Show maximum detail</p>
+<p>--log
+: Show recent log entries</p>
+<p>--limit=LIMIT
+: Limit number of log entries</p>
+<h3><a name="_connection_options"></a>Connection Options</h3>
+<p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default 0.0.0.0)</p>
+<p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+<h2><a name="_output_columns"></a>OUTPUT COLUMNS</h2>
+<h3><a name="_qdstat_c"></a>qdstat -c</h3>
+<dl>
+<dt>
id
</dt>
<dd>
@@ -933,7 +176,7 @@ id
Unique connection identifier
</p>
</dd>
-<dt class="hdlist1">
+<dt>
host
</dt>
<dd>
@@ -941,7 +184,7 @@ host
The hostname or internet address of the remotely connected AMQP container
</p>
</dd>
-<dt class="hdlist1">
+<dt>
container
</dt>
<dd>
@@ -949,14 +192,14 @@ container
The container-name of the remotely connected AMQP container
</p>
</dd>
-<dt class="hdlist1">
+<dt>
role
</dt>
<dd>
<p>
The configured role of the connection
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
normal - Normal connections from client to router
@@ -972,16 +215,16 @@ inter-router - Connection between routers to form a network
route-container - Connection to/from a Broker or other host to receive link-routes and waypoints
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of connection establishment
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - The connection was initiated by the remote container
@@ -992,9 +235,9 @@ in - The connection was initiated by the remote container
out - The connection was initiated by this router
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
security
</dt>
<dd>
@@ -1003,7 +246,7 @@ A description of the security/encryption in effect for this
connection
</p>
</dd>
-<dt class="hdlist1">
+<dt>
authentication
</dt>
<dd>
@@ -1012,19 +255,17 @@ The method and user-id of the authenticated user for
this connection
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_l">qdstat -l</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_l"></a>qdstat -l</h3>
+<dl>
+<dt>
type
</dt>
<dd>
<p>
Type of link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
router-control - An inter-router link that is reserved for control messages exchanged between routers
@@ -1040,16 +281,16 @@ inter-router - An inter-router link that is used for normal message-routed deliv
endpoint - A normal link to an external endpoint container
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of message flow on the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - Deliveries flow inbound to the router
@@ -1060,9 +301,9 @@ in - Deliveries flow inbound to the router
out - Deliveries flow outbound from the router
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
conn id
</dt>
<dd>
@@ -1071,7 +312,7 @@ Unique identifier of the connection over which this link is
attached
</p>
</dd>
-<dt class="hdlist1">
+<dt>
id
</dt>
<dd>
@@ -1079,7 +320,7 @@ id
Unique identifier of this link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
peer
</dt>
<dd>
@@ -1088,7 +329,7 @@ For link-routed links, the unique identifier of the peer link. In
link routing, an inbound link is paired with an outbound link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
class
</dt>
<dd>
@@ -1096,7 +337,7 @@ class
Class of the address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
addr
</dt>
<dd>
@@ -1104,7 +345,7 @@ addr
The address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -1112,7 +353,7 @@ phs
The phase of the address bound to the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cap
</dt>
<dd>
@@ -1120,7 +361,7 @@ cap
The capacity, in deliveries, of the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
undel
</dt>
<dd>
@@ -1128,7 +369,7 @@ undel
The number of undelivered messages stored on the link’s FIFO
</p>
</dd>
-<dt class="hdlist1">
+<dt>
unsettled
</dt>
<dd>
@@ -1136,7 +377,7 @@ unsettled
The number of unsettled deliveries being tracked by the link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
deliveries
</dt>
<dd>
@@ -1144,14 +385,14 @@ deliveries
The total number of deliveries that have transited this link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
admin
</dt>
<dd>
<p>
The administrative status of the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
enabled - The link is enabled for normal operation
@@ -1162,16 +403,16 @@ enabled - The link is enabled for normal operation
disabled - The link is disabled and should be quiescing or stopped (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
oper
</dt>
<dd>
<p>
The operational status of the link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
up - The link is operational
@@ -1192,9 +433,9 @@ quiescing - The link is in the process of quiescing (not yet supported)
idle - The link has completed quiescing and is idle (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
name
</dt>
<dd>
@@ -1202,11 +443,10 @@ name
The link name (only shown if the -v option is provided)
</p>
</dd>
-</dl></div>
-<div class="sect3">
-<h4 id="_qdstat_n">qdstat -n</h4>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h4><a name="_qdstat_n"></a>qdstat -n</h4>
+<dl>
+<dt>
router-id
</dt>
<dd>
@@ -1214,7 +454,7 @@ router-id
Identifier of the router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
next-hop
</dt>
<dd>
@@ -1222,7 +462,7 @@ next-hop
If this router is not a neighbor, identifies the next-hop neighbor used to reach this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
link
</dt>
<dd>
@@ -1230,7 +470,7 @@ link
Unique identifier of the link to the neighbor router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cost
</dt>
<dd>
@@ -1238,7 +478,7 @@ cost
The topology cost to this remote router (with -v option only)
</p>
</dd>
-<dt class="hdlist1">
+<dt>
neighbors
</dt>
<dd>
@@ -1246,7 +486,7 @@ neighbors
The list of neighbor routers (the router’s link-state) (with -v option only)
</p>
</dd>
-<dt class="hdlist1">
+<dt>
valid-origins
</dt>
<dd>
@@ -1254,20 +494,17 @@ valid-origins
The list of origin routers for which the best path to the listed router passes through this router (with -v option only)
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_a">qdstat -a</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_a"></a>qdstat -a</h3>
+<dl>
+<dt>
class
</dt>
<dd>
<p>
The class of the listed address
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
local - Address that is local to this router
@@ -1288,9 +525,9 @@ router - A summary router address used to route messages to a remote router̵
mobile - A mobile address for an attached consumer or producer
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
addr
</dt>
<dd>
@@ -1298,7 +535,7 @@ addr
The address text
</p>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -1306,14 +543,14 @@ phs
For mobile addresses only, the phase of the address. Direct addresses have only a phase 0. Waypoint addresses have multiple phases, normally 0 and 1.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
distrib
</dt>
<dd>
<p>
Distribution method used for this address
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
multicast - A copy of each message is delivered once to each consumer for the address
@@ -1334,9 +571,9 @@ balanced - Each message is delivered to only one consumer for the address. The
flood - Used only for router-control traffic. This is multicast without prevention of duplicate deliveries.
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
in-proc
</dt>
<dd>
@@ -1344,7 +581,7 @@ in-proc
The number of in-process consumers for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
local
</dt>
<dd>
@@ -1352,7 +589,7 @@ local
The number of local (on this router) consumers for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
remote
</dt>
<dd>
@@ -1360,7 +597,7 @@ remote
The number of remote routers that have at least one consumer for this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
cntnr
</dt>
<dd>
@@ -1368,7 +605,7 @@ cntnr
The number of locally attached containers that are destinations for link-routes on this address
</p>
</dd>
-<dt class="hdlist1">
+<dt>
in
</dt>
<dd>
@@ -1376,7 +613,7 @@ in
The number of deliveries for this address that entered the network on this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
out
</dt>
<dd>
@@ -1384,7 +621,7 @@ out
The number of deliveries for this address that exited the network on this router
</p>
</dd>
-<dt class="hdlist1">
+<dt>
thru
</dt>
<dd>
@@ -1392,7 +629,7 @@ thru
The number of deliveries for this address that were forwarded to other routers
</p>
</dd>
-<dt class="hdlist1">
+<dt>
to-proc
</dt>
<dd>
@@ -1400,7 +637,7 @@ to-proc
The number of deliveries for this address that were delivered to an in-process consumer
</p>
</dd>
-<dt class="hdlist1">
+<dt>
from-proc
</dt>
<dd>
@@ -1408,12 +645,10 @@ from-proc
The number of deliveries for this address that were received from an in-process producer
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qdstat_linkroutes">qdstat --linkroutes</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qdstat_linkroutes"></a>qdstat --linkroutes</h3>
+<dl>
+<dt>
prefix
</dt>
<dd>
@@ -1421,7 +656,7 @@ prefix
The prefix for matching addresses of routed links
</p>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
@@ -1429,29 +664,29 @@ dir
The direction (from the router’s perspective) of matching links
</p>
</dd>
-<dt class="hdlist1">
+<dt>
distrib
</dt>
<dd>
<p>
The distribution method used for routed links
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
linkBalanced - the only supported distribution for routed links
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
status
</dt>
<dd>
<p>
Operational status of the link route
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
active - Route is actively routing attaches (i.e. ready for use)
@@ -1462,14 +697,12 @@ active - Route is actively routing attaches (i.e. ready for use)
inactive - Route is inactive because there is no local destination connected
</p>
</li>
-</ul></div>
+</ul>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_qstat_autolinks">qstat --autolinks</h3>
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h3><a name="_qstat_autolinks"></a>qstat --autolinks</h3>
+<dl>
+<dt>
addr
</dt>
<dd>
@@ -1477,14 +710,14 @@ addr
The address of the auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
dir
</dt>
<dd>
<p>
The direction of message flow for the auto link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
in - Messages flow in from the route-container to the router network
@@ -1495,9 +728,9 @@ in - Messages flow in from the route-container to the router network
out - Messages flow out to the route-container from the router network
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
phs
</dt>
<dd>
@@ -1505,7 +738,7 @@ phs
Phase of the address for this auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
link
</dt>
<dd>
@@ -1513,14 +746,14 @@ link
Unique identifier of the link managed by this auto link
</p>
</dd>
-<dt class="hdlist1">
+<dt>
status
</dt>
<dd>
<p>
The operational status of this auto link
</p>
-<div class="ulist"><ul>
+<ul>
<li>
<p>
inactive - There is no connected container for this auto link
@@ -1551,9 +784,9 @@ quiescing - The link is quiescing (not yet supported)
idle - The link is idle (not yet supported)
</p>
</li>
-</ul></div>
+</ul>
</dd>
-<dt class="hdlist1">
+<dt>
lastErr
</dt>
<dd>
@@ -1561,26 +794,10 @@ lastErr
The description of the last attach failure that occurred on this auto link
</p>
</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdmanage(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd(8)</b>, <b>qdmanage(8)</b>, <b>qdrouterd.conf(5)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
<hr/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[11/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
DISPATCH-399: Generate raw HTML body version of dispatch doc.
Generate raw HTML version of dispatch doc for Qpid site.
Project: http://git-wip-us.apache.org/repos/asf/qpid-site/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-site/commit/18828d3b
Tree: http://git-wip-us.apache.org/repos/asf/qpid-site/tree/18828d3b
Diff: http://git-wip-us.apache.org/repos/asf/qpid-site/diff/18828d3b
Branch: refs/heads/asf-site
Commit: 18828d3b52995ec8d00b34d8478cfaa3ee6bb43c
Parents: 3e3e9ea
Author: Alan Conway <ac...@redhat.com>
Authored: Thu Jun 30 15:39:54 2016 -0400
Committer: Alan Conway <ac...@redhat.com>
Committed: Thu Jun 30 15:47:11 2016 -0400
----------------------------------------------------------------------
content/releases/qpid-dispatch-master/book.html | 2827 ++++-------
content/releases/qpid-dispatch-master/book.pdf | Bin 533557 -> 532500 bytes
.../releases/qpid-dispatch-master/index.html | 2 +-
.../qpid-dispatch-master/qdmanage.8.html | 992 +---
.../qpid-dispatch-master/qdrouterd.8.html | 821 +---
.../qpid-dispatch-master/qdrouterd.conf.5.html | 1534 ++----
.../releases/qpid-dispatch-master/qdstat.8.html | 1073 +----
input/releases/qpid-dispatch-master/book.html | 4406 ------------------
.../releases/qpid-dispatch-master/book.html.in | 2823 ++++-------
input/releases/qpid-dispatch-master/book.pdf | Bin 533557 -> 532500 bytes
input/releases/qpid-dispatch-master/index.md | 2 +-
.../qpid-dispatch-master/qdmanage.8.html | 988 ----
.../qpid-dispatch-master/qdmanage.8.html.in | 990 +---
.../qpid-dispatch-master/qdrouterd.8.html | 806 ----
.../qpid-dispatch-master/qdrouterd.8.html.in | 819 +---
.../qpid-dispatch-master/qdrouterd.conf.5.html | 1806 -------
.../qdrouterd.conf.5.html.in | 1532 ++----
.../releases/qpid-dispatch-master/qdstat.8.html | 1467 ------
.../qpid-dispatch-master/qdstat.8.html.in | 1071 +----
scripts/gen-dispatch-release-books | 13 +-
20 files changed, 3090 insertions(+), 20882 deletions(-)
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[09/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/index.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/index.html b/content/releases/qpid-dispatch-master/index.html
index 654a229..2d1eda6 100644
--- a/content/releases/qpid-dispatch-master/index.html
+++ b/content/releases/qpid-dispatch-master/index.html
@@ -124,7 +124,7 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
incomplete. For a smoother experience, see the <a href="/releases/qpid-dispatch-0.6.0/index.html">current stable
release</a>.</p>
-<p>This content was generated at 12:42 on Thursday, 23 June 2016.</p>
+<p>This content was generated at 15:45 on Thursday, 30 June 2016.</p>
</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/qdmanage.8.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/qdmanage.8.html b/content/releases/qpid-dispatch-master/qdmanage.8.html
index b371a93..41083da 100644
--- a/content/releases/qpid-dispatch-master/qdmanage.8.html
+++ b/content/releases/qpid-dispatch-master/qdmanage.8.html
@@ -114,854 +114,96 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>NAME</li></ul>
<div id="-middle-content">
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qmanage(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qmanage(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
+ <h2>NAME</h2>
<p>qdmanage -
management client to control or query qdrouterd(8)
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdmanage</strong> [<em>OPTIONS</em>] <em>OPERATION</em> [<em>ARGUMENTS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>An AMQP management client for use with qdrouterd. Sends AMQP management
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdmanage</strong> [<b>OPTIONS</b>] <b>OPERATION</b> [<b>ARGUMENTS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>An AMQP management client for use with qdrouterd. Sends AMQP management
operations requests and prints the response in JSON format. This is a
generic AMQP management tool and can be used with any standard AMQP
-managed endpoint, not just with qdrouter.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>--type=TYPE
-: Type of entity to operate on.</p></div>
-<div class="paragraph"><p>--name=NAME
-: Name of entity to operate on.</p></div>
-<div class="paragraph"><p>--identity=ID
-: Identity of entity to operate on.</p></div>
-<div class="paragraph"><p>--indent=INDENT
-: Pretty-printing indent. -1 means don’t pretty-print (default 2)</p></div>
-<div class="paragraph"><p>--stdin
-: Read attributes as JSON map or list of maps from stdin.</p></div>
-<div class="paragraph"><p>--body=BODY
-: JSON value to use as body of a non-standard operation call.</p></div>
-<div class="paragraph"><p>--properties=PROPERTIES
-: JSON map to use as properties for a non-standard operation call.</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_operations">OPERATIONS</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<code>query</code> [<em>ATTR</em>…]
+managed endpoint, not just with qdrouter.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-h, --help
+: show this help message and exit</p>
+<p>--version
+: Print version and exit.</p>
+<p>--type=TYPE
+: Type of entity to operate on.</p>
+<p>--name=NAME
+: Name of entity to operate on.</p>
+<p>--identity=ID
+: Identity of entity to operate on.</p>
+<p>--indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print (default 2)</p>
+<p>--stdin
+: Read attributes as JSON map or list of maps from stdin.</p>
+<p>--body=BODY
+: JSON value to use as body of a non-standard operation call.</p>
+<p>--properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p>
+<h3><a name="_connection_options"></a>Connection Options</h3>
+<p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default 0.0.0.0)</p>
+<p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+<h2><a name="_operations"></a>OPERATIONS</h2>
+<dl>
+<dt>
+<code>query</code> [<b>ATTR</b>…]
</dt>
<dd>
<p>
- Print the attributes named in the ATTR list or all attributes if none
- are listed. Print attributes for all entities by default, use --type,
- --name and --identity options to restrict what is printed.
+ Print attributes for multiple entities. Prints all entities by default, use
+ --type, --name or --identity options to restrict which entities are printed.
+ Prints the attributes named in the ATTR list, or all attributes if none are
+ listed.
</p>
</dd>
-<dt class="hdlist1">
-<code>create</code> [<em>ATTR=VALUE</em>…]
+<dt>
+<code>create</code> [<b>ATTR=VALUE</b>…]
</dt>
<dd>
<p>
Create a new entity with the specified attributes. With the --stdin
option, read attributes from stdin. This can be a JSON map of
attributes to create a single entity, or a JSON list of maps to create
- multiple entitiees.
+ multiple entities.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>read</code>
</dt>
<dd>
<p>
- Print the attributes of an entity specified by the --name or
- --identity options. With the --stdin option, create entities based on
- data from stdin. This can be a JSON map of attributes to create a
- single entity, or a JSON list of maps to create multiple entitiees.
+ Print all the attributes of a single entity, specified by the --name or
+ --identity options.
</p>
</dd>
-<dt class="hdlist1">
-<code>update</code> [<em>ATTR=VALUE</em>…]
+<dt>
+<code>update</code> [<b>ATTR=VALUE</b>…]
</dt>
<dd>
<p>
- Update the attributes of an existing entity. With the --stdin option,
- read attributes from stdin. This can be a JSON map of attributes to
- update a single entity, or a JSON list of maps to update multiple
- entitiees. If an ATTR name is listed with no =VALUE, that attribute
- will be deleted from the entity.
+ Update the attributes of an existing entity. If an ATTR name is listed with
+ no =VALUE, that attribute will be deleted from the entity. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of attributes to
+ update a single entity, or a JSON list of maps to update multiple entities.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>delete</code>
</dt>
<dd>
@@ -969,8 +211,8 @@ managed endpoint, not just with qdrouter.</p></div>
Delete an entity specified by the --name or --identity options.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-types</code> [<em>TYPE</em>]
+<dt>
+<code>get-types</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -978,8 +220,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-operations</code> [<em>TYPE</em>]
+<dt>
+<code>get-operations</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -987,8 +229,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-attributes</code> [<em>TYPE</em>]
+<dt>
+<code>get-attributes</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -996,8 +238,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-annotations</code> [<em>TYPE</em>]
+<dt>
+<code>get-annotations</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -1005,7 +247,7 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>get-mgmt-nodes</code>
</dt>
<dd>
@@ -1013,8 +255,8 @@ managed endpoint, not just with qdrouter.</p></div>
List all other known management nodes connected to this one.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-json-schema</code> [<em>INDENT</em>]
+<dt>
+<code>get-json-schema</code> [<b>INDENT</b>]
</dt>
<dd>
<p>
@@ -1022,22 +264,18 @@ managed endpoint, not just with qdrouter.</p></div>
formatted output.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-log</code> [<em>INDENT</em>]
+<dt>
+<code>get-log</code> [<b>INDENT</b>]
</dt>
<dd>
<p>
Get recent log entries from the router.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h2><a name="_files"></a>FILES</h2>
+<dl>
+<dt>
/usr/local/share/doc/qpid-dispatch/qdrouter.json
</dt>
<dd>
@@ -1045,7 +283,7 @@ managed endpoint, not just with qdrouter.</p></div>
Management schema for qdrouterd.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt
</dt>
<dd>
@@ -1053,55 +291,31 @@ managed endpoint, not just with qdrouter.</p></div>
Explanation of the management schema.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_examples">EXAMPLES</h2>
-<div class="sectionbody">
-<div class="listingblock">
-<div class="title">Show the logging configuration</div>
-<div class="content">
+</dl>
+<h2><a name="_examples"></a>EXAMPLES</h2>
+<p><b>Show the logging configuration</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>qdmanage query --type=log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable debug and higher log messages by default:</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable trace log messages only for the MESSAGE moudle and direct MESSAGE logs to the file "test.log"</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Set MESSAGE logging back to the default</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=default</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Disable MESSAGE logging</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=none</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</td></tr></table>
+<p><b>Enable debug and higher log messages by default:</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/DEFAULT enable=debug+</code></pre>
+</td></tr></table>
+<p><b>Enable trace log messages only for the MESSAGE module and direct MESSAGE logs to the file "test.log"</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=trace output=test.log</code></pre>
+</td></tr></table>
+<p><b>Set MESSAGE logging back to the default</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=default</code></pre>
+</td></tr></table>
+<p><b>Disable MESSAGE logging</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=none</code></pre>
+</td></tr></table>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd(8)</b>, <b>qdstat(8)</b>, <b>qdrouterd.conf(5)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
<hr/>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/qdrouterd.8.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/qdrouterd.8.html b/content/releases/qpid-dispatch-master/qdrouterd.8.html
index 990eaed..e6fb782 100644
--- a/content/releases/qpid-dispatch-master/qdrouterd.8.html
+++ b/content/releases/qpid-dispatch-master/qdrouterd.8.html
@@ -114,786 +114,32 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>NAME</li></ul>
<div id="-middle-content">
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
+ <h2>NAME</h2>
<p>qdrouterd -
routes AMQP messages.
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdrouterd</strong> [<b>OPTIONS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
AMQP 1.0 messages between endpoints, such as messaging clients and
-servers.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
-: Load configuration from file at PATH</p></div>
-<div class="paragraph"><p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
-: Location of Dispatch’s Python library</p></div>
-<div class="paragraph"><p>-d, --daemon
-: Run process as a SysV-style daemon</p></div>
-<div class="paragraph"><p>-P, --pidfile
-: If daemon, the file for the stored daemon pid</p></div>
-<div class="paragraph"><p>-U, --user
-: If daemon, the username to run as</p></div>
-<div class="paragraph"><p>-h, --help
-: Print this help</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
+servers.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
+: Load configuration from file at PATH</p>
+<p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
+: Location of Dispatch’s Python library</p>
+<p>-d, --daemon
+: Run process as a SysV-style daemon</p>
+<p>-P, --pidfile
+: If daemon, the file for the stored daemon pid</p>
+<p>-U, --user
+: If daemon, the username to run as</p>
+<p>-h, --help
+: Print this help</p>
+<h2><a name="_files"></a>FILES</h2>
+<dl>
+<dt>
/usr/local/etc/qdrouterd.conf
</dt>
<dd>
@@ -901,25 +147,10 @@ servers.</p></div>
Configuration flie.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd.conf(5)</b>, <b>qdstat(8)</b>, <b>qdmanage(8)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
<hr/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[04/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/index.md
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/index.md b/input/releases/qpid-dispatch-master/index.md
index 4a6f250..775e7a4 100644
--- a/input/releases/qpid-dispatch-master/index.md
+++ b/input/releases/qpid-dispatch-master/index.md
@@ -27,7 +27,7 @@ Code and documentation found here may be unstable, incorrect, or
incomplete. For a smoother experience, see the [current stable
release]({{current_dispatch_release_url}}/index.html).
-This content was generated at 12:42 on Thursday, 23 June 2016.
+This content was generated at 15:45 on Thursday, 30 June 2016.
</div>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdmanage.8.html
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdmanage.8.html b/input/releases/qpid-dispatch-master/qdmanage.8.html
deleted file mode 100644
index 9f9244d..0000000
--- a/input/releases/qpid-dispatch-master/qdmanage.8.html
+++ /dev/null
@@ -1,988 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qmanage(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qmanage(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
-<p>qdmanage -
- management client to control or query qdrouterd(8)
-</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdmanage</strong> [<em>OPTIONS</em>] <em>OPERATION</em> [<em>ARGUMENTS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>An AMQP management client for use with qdrouterd. Sends AMQP management
-operations requests and prints the response in JSON format. This is a
-generic AMQP management tool and can be used with any standard AMQP
-managed endpoint, not just with qdrouter.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>--type=TYPE
-: Type of entity to operate on.</p></div>
-<div class="paragraph"><p>--name=NAME
-: Name of entity to operate on.</p></div>
-<div class="paragraph"><p>--identity=ID
-: Identity of entity to operate on.</p></div>
-<div class="paragraph"><p>--indent=INDENT
-: Pretty-printing indent. -1 means don’t pretty-print (default 2)</p></div>
-<div class="paragraph"><p>--stdin
-: Read attributes as JSON map or list of maps from stdin.</p></div>
-<div class="paragraph"><p>--body=BODY
-: JSON value to use as body of a non-standard operation call.</p></div>
-<div class="paragraph"><p>--properties=PROPERTIES
-: JSON map to use as properties for a non-standard operation call.</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_operations">OPERATIONS</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<code>query</code> [<em>ATTR</em>…]
-</dt>
-<dd>
-<p>
- Print the attributes named in the ATTR list or all attributes if none
- are listed. Print attributes for all entities by default, use --type,
- --name and --identity options to restrict what is printed.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>create</code> [<em>ATTR=VALUE</em>…]
-</dt>
-<dd>
-<p>
- Create a new entity with the specified attributes. With the --stdin
- option, read attributes from stdin. This can be a JSON map of
- attributes to create a single entity, or a JSON list of maps to create
- multiple entitiees.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>read</code>
-</dt>
-<dd>
-<p>
- Print the attributes of an entity specified by the --name or
- --identity options. With the --stdin option, create entities based on
- data from stdin. This can be a JSON map of attributes to create a
- single entity, or a JSON list of maps to create multiple entitiees.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>update</code> [<em>ATTR=VALUE</em>…]
-</dt>
-<dd>
-<p>
- Update the attributes of an existing entity. With the --stdin option,
- read attributes from stdin. This can be a JSON map of attributes to
- update a single entity, or a JSON list of maps to update multiple
- entitiees. If an ATTR name is listed with no =VALUE, that attribute
- will be deleted from the entity.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>delete</code>
-</dt>
-<dd>
-<p>
- Delete an entity specified by the --name or --identity options.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-types</code> [<em>TYPE</em>]
-</dt>
-<dd>
-<p>
- List entity types with their base types. With no arguments list all
- types.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-operations</code> [<em>TYPE</em>]
-</dt>
-<dd>
-<p>
- List entity types with their operations. With no arguments list all
- types.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-attributes</code> [<em>TYPE</em>]
-</dt>
-<dd>
-<p>
- List entity types with their attributes. With no arguments list all
- types.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-annotations</code> [<em>TYPE</em>]
-</dt>
-<dd>
-<p>
- List entity types with their annotations. With no arguments list all
- types.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-mgmt-nodes</code>
-</dt>
-<dd>
-<p>
- List all other known management nodes connected to this one.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-json-schema</code> [<em>INDENT</em>]
-</dt>
-<dd>
-<p>
- Get the router schema in JSON format. Optional integer indent for
- formatted output.
-</p>
-</dd>
-<dt class="hdlist1">
-<code>get-log</code> [<em>INDENT</em>]
-</dt>
-<dd>
-<p>
- Get recent log entries from the router.
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
-/usr/local/share/doc/qpid-dispatch/qdrouter.json
-</dt>
-<dd>
-<p>
- Management schema for qdrouterd.
-</p>
-</dd>
-<dt class="hdlist1">
-/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt
-</dt>
-<dd>
-<p>
- Explanation of the management schema.
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_examples">EXAMPLES</h2>
-<div class="sectionbody">
-<div class="listingblock">
-<div class="title">Show the logging configuration</div>
-<div class="content">
-<pre><code>qdmanage query --type=log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable debug and higher log messages by default:</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable trace log messages only for the MESSAGE moudle and direct MESSAGE logs to the file "test.log"</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Set MESSAGE logging back to the default</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=default</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Disable MESSAGE logging</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=none</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdmanage.8.html.in
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdmanage.8.html.in b/input/releases/qpid-dispatch-master/qdmanage.8.html.in
index 9f9244d..82a43f8 100644
--- a/input/releases/qpid-dispatch-master/qdmanage.8.html.in
+++ b/input/releases/qpid-dispatch-master/qdmanage.8.html.in
@@ -1,851 +1,93 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qmanage(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qmanage(8) Manual Page
-</h1>
<h2>NAME</h2>
-<div class="sectionbody">
<p>qdmanage -
management client to control or query qdrouterd(8)
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdmanage</strong> [<em>OPTIONS</em>] <em>OPERATION</em> [<em>ARGUMENTS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>An AMQP management client for use with qdrouterd. Sends AMQP management
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p><strong>qdmanage</strong> [<b>OPTIONS</b>] <b>OPERATION</b> [<b>ARGUMENTS</b>]</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>An AMQP management client for use with qdrouterd. Sends AMQP management
operations requests and prints the response in JSON format. This is a
generic AMQP management tool and can be used with any standard AMQP
-managed endpoint, not just with qdrouter.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-h, --help
-: show this help message and exit</p></div>
-<div class="paragraph"><p>--version
-: Print version and exit.</p></div>
-<div class="paragraph"><p>--type=TYPE
-: Type of entity to operate on.</p></div>
-<div class="paragraph"><p>--name=NAME
-: Name of entity to operate on.</p></div>
-<div class="paragraph"><p>--identity=ID
-: Identity of entity to operate on.</p></div>
-<div class="paragraph"><p>--indent=INDENT
-: Pretty-printing indent. -1 means don’t pretty-print (default 2)</p></div>
-<div class="paragraph"><p>--stdin
-: Read attributes as JSON map or list of maps from stdin.</p></div>
-<div class="paragraph"><p>--body=BODY
-: JSON value to use as body of a non-standard operation call.</p></div>
-<div class="paragraph"><p>--properties=PROPERTIES
-: JSON map to use as properties for a non-standard operation call.</p></div>
-<div class="sect2">
-<h3 id="_connection_options">Connection Options</h3>
-<div class="paragraph"><p>-b URL, --bus=URL
-: URL of the messaging bus to connect to (default 0.0.0.0)</p></div>
-<div class="paragraph"><p>-r ROUTER-ID, --router=ROUTER-ID
-: Router to be queried</p></div>
-<div class="paragraph"><p>-t SECS, --timeout=SECS
-: Maximum time to wait for connection in seconds (default 5)</p></div>
-<div class="paragraph"><p>--ssl-certificate=CERT
-: Client SSL certificate (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-key=KEY
-: Client SSL private key (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-trustfile=TRUSTED-CA-DB
-: Trusted Certificate Authority Database file (PEM Format)</p></div>
-<div class="paragraph"><p>--ssl-password=PASSWORD
-: Certificate password, will be prompted if not specifed.</p></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_operations">OPERATIONS</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<code>query</code> [<em>ATTR</em>…]
+managed endpoint, not just with qdrouter.</p>
+<h2><a name="_options"></a>OPTIONS</h2>
+<p>-h, --help
+: show this help message and exit</p>
+<p>--version
+: Print version and exit.</p>
+<p>--type=TYPE
+: Type of entity to operate on.</p>
+<p>--name=NAME
+: Name of entity to operate on.</p>
+<p>--identity=ID
+: Identity of entity to operate on.</p>
+<p>--indent=INDENT
+: Pretty-printing indent. -1 means don’t pretty-print (default 2)</p>
+<p>--stdin
+: Read attributes as JSON map or list of maps from stdin.</p>
+<p>--body=BODY
+: JSON value to use as body of a non-standard operation call.</p>
+<p>--properties=PROPERTIES
+: JSON map to use as properties for a non-standard operation call.</p>
+<h3><a name="_connection_options"></a>Connection Options</h3>
+<p>-b URL, --bus=URL
+: URL of the messaging bus to connect to (default 0.0.0.0)</p>
+<p>-r ROUTER-ID, --router=ROUTER-ID
+: Router to be queried</p>
+<p>-t SECS, --timeout=SECS
+: Maximum time to wait for connection in seconds (default 5)</p>
+<p>--ssl-certificate=CERT
+: Client SSL certificate (PEM Format)</p>
+<p>--ssl-key=KEY
+: Client SSL private key (PEM Format)</p>
+<p>--ssl-trustfile=TRUSTED-CA-DB
+: Trusted Certificate Authority Database file (PEM Format)</p>
+<p>--ssl-password=PASSWORD
+: Certificate password, will be prompted if not specifed.</p>
+<h2><a name="_operations"></a>OPERATIONS</h2>
+<dl>
+<dt>
+<code>query</code> [<b>ATTR</b>…]
</dt>
<dd>
<p>
- Print the attributes named in the ATTR list or all attributes if none
- are listed. Print attributes for all entities by default, use --type,
- --name and --identity options to restrict what is printed.
+ Print attributes for multiple entities. Prints all entities by default, use
+ --type, --name or --identity options to restrict which entities are printed.
+ Prints the attributes named in the ATTR list, or all attributes if none are
+ listed.
</p>
</dd>
-<dt class="hdlist1">
-<code>create</code> [<em>ATTR=VALUE</em>…]
+<dt>
+<code>create</code> [<b>ATTR=VALUE</b>…]
</dt>
<dd>
<p>
Create a new entity with the specified attributes. With the --stdin
option, read attributes from stdin. This can be a JSON map of
attributes to create a single entity, or a JSON list of maps to create
- multiple entitiees.
+ multiple entities.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>read</code>
</dt>
<dd>
<p>
- Print the attributes of an entity specified by the --name or
- --identity options. With the --stdin option, create entities based on
- data from stdin. This can be a JSON map of attributes to create a
- single entity, or a JSON list of maps to create multiple entitiees.
+ Print all the attributes of a single entity, specified by the --name or
+ --identity options.
</p>
</dd>
-<dt class="hdlist1">
-<code>update</code> [<em>ATTR=VALUE</em>…]
+<dt>
+<code>update</code> [<b>ATTR=VALUE</b>…]
</dt>
<dd>
<p>
- Update the attributes of an existing entity. With the --stdin option,
- read attributes from stdin. This can be a JSON map of attributes to
- update a single entity, or a JSON list of maps to update multiple
- entitiees. If an ATTR name is listed with no =VALUE, that attribute
- will be deleted from the entity.
+ Update the attributes of an existing entity. If an ATTR name is listed with
+ no =VALUE, that attribute will be deleted from the entity. With the --stdin
+ option, read attributes from stdin. This can be a JSON map of attributes to
+ update a single entity, or a JSON list of maps to update multiple entities.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>delete</code>
</dt>
<dd>
@@ -853,8 +95,8 @@ managed endpoint, not just with qdrouter.</p></div>
Delete an entity specified by the --name or --identity options.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-types</code> [<em>TYPE</em>]
+<dt>
+<code>get-types</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -862,8 +104,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-operations</code> [<em>TYPE</em>]
+<dt>
+<code>get-operations</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -871,8 +113,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-attributes</code> [<em>TYPE</em>]
+<dt>
+<code>get-attributes</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -880,8 +122,8 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-annotations</code> [<em>TYPE</em>]
+<dt>
+<code>get-annotations</code> [<b>TYPE</b>]
</dt>
<dd>
<p>
@@ -889,7 +131,7 @@ managed endpoint, not just with qdrouter.</p></div>
types.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
<code>get-mgmt-nodes</code>
</dt>
<dd>
@@ -897,8 +139,8 @@ managed endpoint, not just with qdrouter.</p></div>
List all other known management nodes connected to this one.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-json-schema</code> [<em>INDENT</em>]
+<dt>
+<code>get-json-schema</code> [<b>INDENT</b>]
</dt>
<dd>
<p>
@@ -906,22 +148,18 @@ managed endpoint, not just with qdrouter.</p></div>
formatted output.
</p>
</dd>
-<dt class="hdlist1">
-<code>get-log</code> [<em>INDENT</em>]
+<dt>
+<code>get-log</code> [<b>INDENT</b>]
</dt>
<dd>
<p>
Get recent log entries from the router.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
+</dl>
+<h2><a name="_files"></a>FILES</h2>
+<dl>
+<dt>
/usr/local/share/doc/qpid-dispatch/qdrouter.json
</dt>
<dd>
@@ -929,7 +167,7 @@ managed endpoint, not just with qdrouter.</p></div>
Management schema for qdrouterd.
</p>
</dd>
-<dt class="hdlist1">
+<dt>
/usr/local/share/doc/qpid-dispatch/qdrouter.json.readme.txt
</dt>
<dd>
@@ -937,52 +175,28 @@ managed endpoint, not just with qdrouter.</p></div>
Explanation of the management schema.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_examples">EXAMPLES</h2>
-<div class="sectionbody">
-<div class="listingblock">
-<div class="title">Show the logging configuration</div>
-<div class="content">
+</dl>
+<h2><a name="_examples"></a>EXAMPLES</h2>
+<p><b>Show the logging configuration</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>qdmanage query --type=log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable debug and higher log messages by default:</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/DEFAULT enable=debug+</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Enable trace log messages only for the MESSAGE moudle and direct MESSAGE logs to the file "test.log"</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=trace output=test.log</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Set MESSAGE logging back to the default</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=default</code></pre>
-</div></div>
-<div class="listingblock">
-<div class="title">Disable MESSAGE logging</div>
-<div class="content">
-<pre><code>qdmanage udpdate name=log/MESSAGE enable=none</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd(8)</em>, <em>qdstat(8)</em>, <em>qdrouterd.conf(5)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
+</td></tr></table>
+<p><b>Enable debug and higher log messages by default:</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/DEFAULT enable=debug+</code></pre>
+</td></tr></table>
+<p><b>Enable trace log messages only for the MESSAGE module and direct MESSAGE logs to the file "test.log"</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=trace output=test.log</code></pre>
+</td></tr></table>
+<p><b>Set MESSAGE logging back to the default</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=default</code></pre>
+</td></tr></table>
+<p><b>Disable MESSAGE logging</b></p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
+<pre><code>qdmanage update name=log/MESSAGE enable=none</code></pre>
+</td></tr></table>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><b>qdrouterd(8)</b>, <b>qdstat(8)</b>, <b>qdrouterd.conf(5)</b></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/input/releases/qpid-dispatch-master/qdrouterd.8.html
----------------------------------------------------------------------
diff --git a/input/releases/qpid-dispatch-master/qdrouterd.8.html b/input/releases/qpid-dispatch-master/qdrouterd.8.html
deleted file mode 100644
index d0449f3..0000000
--- a/input/releases/qpid-dispatch-master/qdrouterd.8.html
+++ /dev/null
@@ -1,806 +0,0 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd(8)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd(8) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
-<p>qdrouterd -
- routes AMQP messages.
-</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd</strong> [<em>OPTIONS</em>]</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The Qpid Dispatch router (qdrouterd) is a network daemon that directs
-AMQP 1.0 messages between endpoints, such as messaging clients and
-servers.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_options">OPTIONS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>-c, --config=PATH (/usr/local/etc/qpid-dispatch/qdrouterd.conf)
-: Load configuration from file at PATH</p></div>
-<div class="paragraph"><p>-I, --include=PATH (/usr/local/lib/qpid-dispatch/python)
-: Location of Dispatch’s Python library</p></div>
-<div class="paragraph"><p>-d, --daemon
-: Run process as a SysV-style daemon</p></div>
-<div class="paragraph"><p>-P, --pidfile
-: If daemon, the file for the stored daemon pid</p></div>
-<div class="paragraph"><p>-U, --user
-: If daemon, the username to run as</p></div>
-<div class="paragraph"><p>-h, --help
-: Print this help</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_files">FILES</h2>
-<div class="sectionbody">
-<div class="dlist"><dl>
-<dt class="hdlist1">
-/usr/local/etc/qdrouterd.conf
-</dt>
-<dd>
-<p>
- Configuration flie.
-</p>
-</dd>
-</dl></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><em>qdrouterd.conf(5)</em>, <em>qdstat(8)</em>, <em>qdmanage(8)</em></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:32:19 EDT
-</div>
-</div>
-</body>
-</html>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org
[08/11] qpid-site git commit: DISPATCH-399: Generate raw HTML body
version of dispatch doc.
Posted by ac...@apache.org.
http://git-wip-us.apache.org/repos/asf/qpid-site/blob/18828d3b/content/releases/qpid-dispatch-master/qdrouterd.conf.5.html
----------------------------------------------------------------------
diff --git a/content/releases/qpid-dispatch-master/qdrouterd.conf.5.html b/content/releases/qpid-dispatch-master/qdrouterd.conf.5.html
index aa0e485..d5d7bc5 100644
--- a/content/releases/qpid-dispatch-master/qdrouterd.conf.5.html
+++ b/content/releases/qpid-dispatch-master/qdrouterd.conf.5.html
@@ -114,791 +114,41 @@ https://github.com/apache/qpid-proton/blob/go1{/dir}/{file}#L{line}"/>
<ul id="-path-navigation"><li><a href="/index.html">Home</a></li><li><a href="/releases/index.html">Releases</a></li><li><a href="/releases/qpid-dispatch-master/index.html">Qpid Dispatch Master</a></li><li>NAME</li></ul>
<div id="-middle-content">
- <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
- "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
-<head>
-<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
-<meta name="generator" content="AsciiDoc 8.6.8" />
-<title>qdrouterd.conf(5)</title>
-<style type="text/css">
-/* Shared CSS for AsciiDoc xhtml11 and html5 backends */
-
-/* Default font. */
-body {
- font-family: Georgia,serif;
-}
-
-/* Title font. */
-h1, h2, h3, h4, h5, h6,
-div.title, caption.title,
-thead, p.table.header,
-#toctitle,
-#author, #revnumber, #revdate, #revremark,
-#footer {
- font-family: Arial,Helvetica,sans-serif;
-}
-
-body {
- margin: 1em 5% 1em 5%;
-}
-
-a {
- color: blue;
- text-decoration: underline;
-}
-a:visited {
- color: fuchsia;
-}
-
-em {
- font-style: italic;
- color: navy;
-}
-
-strong {
- font-weight: bold;
- color: #083194;
-}
-
-h1, h2, h3, h4, h5, h6 {
- color: #527bbd;
- margin-top: 1.2em;
- margin-bottom: 0.5em;
- line-height: 1.3;
-}
-
-h1, h2, h3 {
- border-bottom: 2px solid silver;
-}
-h2 {
- padding-top: 0.5em;
-}
-h3 {
- float: left;
-}
-h3 + * {
- clear: left;
-}
-h5 {
- font-size: 1.0em;
-}
-
-div.sectionbody {
- margin-left: 0;
-}
-
-hr {
- border: 1px solid silver;
-}
-
-p {
- margin-top: 0.5em;
- margin-bottom: 0.5em;
-}
-
-ul, ol, li > p {
- margin-top: 0;
-}
-ul > li { color: #aaa; }
-ul > li > * { color: black; }
-
-.monospaced, code, pre {
- font-family: "Courier New", Courier, monospace;
- font-size: inherit;
- color: navy;
- padding: 0;
- margin: 0;
-}
-
-
-#author {
- color: #527bbd;
- font-weight: bold;
- font-size: 1.1em;
-}
-#email {
-}
-#revnumber, #revdate, #revremark {
-}
-
-#footer {
- font-size: small;
- border-top: 2px solid silver;
- padding-top: 0.5em;
- margin-top: 4.0em;
-}
-#footer-text {
- float: left;
- padding-bottom: 0.5em;
-}
-#footer-badges {
- float: right;
- padding-bottom: 0.5em;
-}
-
-#preamble {
- margin-top: 1.5em;
- margin-bottom: 1.5em;
-}
-div.imageblock, div.exampleblock, div.verseblock,
-div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
-div.admonitionblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.admonitionblock {
- margin-top: 2.0em;
- margin-bottom: 2.0em;
- margin-right: 10%;
- color: #606060;
-}
-
-div.content { /* Block element content. */
- padding: 0;
-}
-
-/* Block element titles. */
-div.title, caption.title {
- color: #527bbd;
- font-weight: bold;
- text-align: left;
- margin-top: 1.0em;
- margin-bottom: 0.5em;
-}
-div.title + * {
- margin-top: 0;
-}
-
-td div.title:first-child {
- margin-top: 0.0em;
-}
-div.content div.title:first-child {
- margin-top: 0.0em;
-}
-div.content + div.title {
- margin-top: 0.0em;
-}
-
-div.sidebarblock > div.content {
- background: #ffffee;
- border: 1px solid #dddddd;
- border-left: 4px solid #f0f0f0;
- padding: 0.5em;
-}
-
-div.listingblock > div.content {
- border: 1px solid #dddddd;
- border-left: 5px solid #f0f0f0;
- background: #f8f8f8;
- padding: 0.5em;
-}
-
-div.quoteblock, div.verseblock {
- padding-left: 1.0em;
- margin-left: 1.0em;
- margin-right: 10%;
- border-left: 5px solid #f0f0f0;
- color: #888;
-}
-
-div.quoteblock > div.attribution {
- padding-top: 0.5em;
- text-align: right;
-}
-
-div.verseblock > pre.content {
- font-family: inherit;
- font-size: inherit;
-}
-div.verseblock > div.attribution {
- padding-top: 0.75em;
- text-align: left;
-}
-/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
-div.verseblock + div.attribution {
- text-align: left;
-}
-
-div.admonitionblock .icon {
- vertical-align: top;
- font-size: 1.1em;
- font-weight: bold;
- text-decoration: underline;
- color: #527bbd;
- padding-right: 0.5em;
-}
-div.admonitionblock td.content {
- padding-left: 0.5em;
- border-left: 3px solid #dddddd;
-}
-
-div.exampleblock > div.content {
- border-left: 3px solid #dddddd;
- padding-left: 0.5em;
-}
-
-div.imageblock div.content { padding-left: 0; }
-span.image img { border-style: none; }
-a.image:visited { color: white; }
-
-dl {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-dt {
- margin-top: 0.5em;
- margin-bottom: 0;
- font-style: normal;
- color: navy;
-}
-dd > *:first-child {
- margin-top: 0.1em;
-}
-
-ul, ol {
- list-style-position: outside;
-}
-ol.arabic {
- list-style-type: decimal;
-}
-ol.loweralpha {
- list-style-type: lower-alpha;
-}
-ol.upperalpha {
- list-style-type: upper-alpha;
-}
-ol.lowerroman {
- list-style-type: lower-roman;
-}
-ol.upperroman {
- list-style-type: upper-roman;
-}
-
-div.compact ul, div.compact ol,
-div.compact p, div.compact p,
-div.compact div, div.compact div {
- margin-top: 0.1em;
- margin-bottom: 0.1em;
-}
-
-tfoot {
- font-weight: bold;
-}
-td > div.verse {
- white-space: pre;
-}
-
-div.hdlist {
- margin-top: 0.8em;
- margin-bottom: 0.8em;
-}
-div.hdlist tr {
- padding-bottom: 15px;
-}
-dt.hdlist1.strong, td.hdlist1.strong {
- font-weight: bold;
-}
-td.hdlist1 {
- vertical-align: top;
- font-style: normal;
- padding-right: 0.8em;
- color: navy;
-}
-td.hdlist2 {
- vertical-align: top;
-}
-div.hdlist.compact tr {
- margin: 0;
- padding-bottom: 0;
-}
-
-.comment {
- background: yellow;
-}
-
-.footnote, .footnoteref {
- font-size: 0.8em;
-}
-
-span.footnote, span.footnoteref {
- vertical-align: super;
-}
-
-#footnotes {
- margin: 20px 0 20px 0;
- padding: 7px 0 0 0;
-}
-
-#footnotes div.footnote {
- margin: 0 0 5px 0;
-}
-
-#footnotes hr {
- border: none;
- border-top: 1px solid silver;
- height: 1px;
- text-align: left;
- margin-left: 0;
- width: 20%;
- min-width: 100px;
-}
-
-div.colist td {
- padding-right: 0.5em;
- padding-bottom: 0.3em;
- vertical-align: top;
-}
-div.colist td img {
- margin-top: 0.3em;
-}
-
-@media print {
- #footer-badges { display: none; }
-}
-
-#toc {
- margin-bottom: 2.5em;
-}
-
-#toctitle {
- color: #527bbd;
- font-size: 1.1em;
- font-weight: bold;
- margin-top: 1.0em;
- margin-bottom: 0.1em;
-}
-
-div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
- margin-top: 0;
- margin-bottom: 0;
-}
-div.toclevel2 {
- margin-left: 2em;
- font-size: 0.9em;
-}
-div.toclevel3 {
- margin-left: 4em;
- font-size: 0.9em;
-}
-div.toclevel4 {
- margin-left: 6em;
- font-size: 0.9em;
-}
-
-span.aqua { color: aqua; }
-span.black { color: black; }
-span.blue { color: blue; }
-span.fuchsia { color: fuchsia; }
-span.gray { color: gray; }
-span.green { color: green; }
-span.lime { color: lime; }
-span.maroon { color: maroon; }
-span.navy { color: navy; }
-span.olive { color: olive; }
-span.purple { color: purple; }
-span.red { color: red; }
-span.silver { color: silver; }
-span.teal { color: teal; }
-span.white { color: white; }
-span.yellow { color: yellow; }
-
-span.aqua-background { background: aqua; }
-span.black-background { background: black; }
-span.blue-background { background: blue; }
-span.fuchsia-background { background: fuchsia; }
-span.gray-background { background: gray; }
-span.green-background { background: green; }
-span.lime-background { background: lime; }
-span.maroon-background { background: maroon; }
-span.navy-background { background: navy; }
-span.olive-background { background: olive; }
-span.purple-background { background: purple; }
-span.red-background { background: red; }
-span.silver-background { background: silver; }
-span.teal-background { background: teal; }
-span.white-background { background: white; }
-span.yellow-background { background: yellow; }
-
-span.big { font-size: 2em; }
-span.small { font-size: 0.6em; }
-
-span.underline { text-decoration: underline; }
-span.overline { text-decoration: overline; }
-span.line-through { text-decoration: line-through; }
-
-div.unbreakable { page-break-inside: avoid; }
-
-
-/*
- * xhtml11 specific
- *
- * */
-
-div.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-div.tableblock > table {
- border: 3px solid #527bbd;
-}
-thead, p.table.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.table {
- margin-top: 0;
-}
-/* Because the table frame attribute is overriden by CSS in most browsers. */
-div.tableblock > table[frame="void"] {
- border-style: none;
-}
-div.tableblock > table[frame="hsides"] {
- border-left-style: none;
- border-right-style: none;
-}
-div.tableblock > table[frame="vsides"] {
- border-top-style: none;
- border-bottom-style: none;
-}
-
-
-/*
- * html5 specific
- *
- * */
-
-table.tableblock {
- margin-top: 1.0em;
- margin-bottom: 1.5em;
-}
-thead, p.tableblock.header {
- font-weight: bold;
- color: #527bbd;
-}
-p.tableblock {
- margin-top: 0;
-}
-table.tableblock {
- border-width: 3px;
- border-spacing: 0px;
- border-style: solid;
- border-color: #527bbd;
- border-collapse: collapse;
-}
-th.tableblock, td.tableblock {
- border-width: 1px;
- padding: 4px;
- border-style: solid;
- border-color: #527bbd;
-}
-
-table.tableblock.frame-topbot {
- border-left-style: hidden;
- border-right-style: hidden;
-}
-table.tableblock.frame-sides {
- border-top-style: hidden;
- border-bottom-style: hidden;
-}
-table.tableblock.frame-none {
- border-style: hidden;
-}
-
-th.tableblock.halign-left, td.tableblock.halign-left {
- text-align: left;
-}
-th.tableblock.halign-center, td.tableblock.halign-center {
- text-align: center;
-}
-th.tableblock.halign-right, td.tableblock.halign-right {
- text-align: right;
-}
-
-th.tableblock.valign-top, td.tableblock.valign-top {
- vertical-align: top;
-}
-th.tableblock.valign-middle, td.tableblock.valign-middle {
- vertical-align: middle;
-}
-th.tableblock.valign-bottom, td.tableblock.valign-bottom {
- vertical-align: bottom;
-}
-
-
-/*
- * manpage specific
- *
- * */
-
-body.manpage h1 {
- padding-top: 0.5em;
- padding-bottom: 0.5em;
- border-top: 2px solid silver;
- border-bottom: 2px solid silver;
-}
-body.manpage h2 {
- border-style: none;
-}
-body.manpage div.sectionbody {
- margin-left: 3em;
-}
-
-@media print {
- body.manpage div#toc { display: none; }
-}
-
-
-</style>
-<script type="text/javascript">
-/*<+'])');
- // Function that scans the DOM tree for header elements (the DOM2
- // nodeIterator API would be a better technique but not supported by all
- // browsers).
- var iterate = function (el) {
- for (var i = el.firstChild; i != null; i = i.nextSibling) {
- if (i.nodeType == 1 /* Node.ELEMENT_NODE */) {
- var mo = re.exec(i.tagName);
- if (mo && (i.getAttribute("class") || i.getAttribute("className")) != "float") {
- result[result.length] = new TocEntry(i, getText(i), mo[1]-1);
- }
- iterate(i);
- }
- }
- }
- iterate(el);
- return result;
- }
-
- var toc = document.getElementById("toc");
- if (!toc) {
- return;
- }
-
- // Delete existing TOC entries in case we're reloading the TOC.
- var tocEntriesToRemove = [];
- var i;
- for (i = 0; i < toc.childNodes.length; i++) {
- var entry = toc.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div'
- && entry.getAttribute("class")
- && entry.getAttribute("class").match(/^toclevel/))
- tocEntriesToRemove.push(entry);
- }
- for (i = 0; i < tocEntriesToRemove.length; i++) {
- toc.removeChild(tocEntriesToRemove[i]);
- }
-
- // Rebuild TOC entries.
- var entries = tocEntries(document.getElementById("content"), toclevels);
- for (var i = 0; i < entries.length; ++i) {
- var entry = entries[i];
- if (entry.element.id == "")
- entry.element.id = "_toc_" + i;
- var a = document.createElement("a");
- a.href = "#" + entry.element.id;
- a.appendChild(document.createTextNode(entry.text));
- var div = document.createElement("div");
- div.appendChild(a);
- div.className = "toclevel" + entry.toclevel;
- toc.appendChild(div);
- }
- if (entries.length == 0)
- toc.parentNode.removeChild(toc);
-},
-
-
-/////////////////////////////////////////////////////////////////////
-// Footnotes generator
-/////////////////////////////////////////////////////////////////////
-
-/* Based on footnote generation code from:
- * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
- */
-
-footnotes: function () {
- // Delete existing footnote entries in case we're reloading the footnodes.
- var i;
- var noteholder = document.getElementById("footnotes");
- if (!noteholder) {
- return;
- }
- var entriesToRemove = [];
- for (i = 0; i < noteholder.childNodes.length; i++) {
- var entry = noteholder.childNodes[i];
- if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
- entriesToRemove.push(entry);
- }
- for (i = 0; i < entriesToRemove.length; i++) {
- noteholder.removeChild(entriesToRemove[i]);
- }
-
- // Rebuild footnote entries.
- var cont = document.getElementById("content");
- var spans = cont.getElementsByTagName("span");
- var refs = {};
- var n = 0;
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnote") {
- n++;
- var note = spans[i].getAttribute("data-note");
- if (!note) {
- // Use [\s\S] in place of . so multi-line matches work.
- // Because JavaScript has no s (dotall) regex flag.
- note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
- spans[i].innerHTML =
- "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- spans[i].setAttribute("data-note", note);
- }
- noteholder.innerHTML +=
- "<div class='footnote' id='_footnote_" + n + "'>" +
- "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
- n + "</a>. " + note + "</div>";
- var id =spans[i].getAttribute("id");
- if (id != null) refs["#"+id] = n;
- }
- }
- if (n == 0)
- noteholder.parentNode.removeChild(noteholder);
- else {
- // Process footnoterefs.
- for (i=0; i<spans.length; i++) {
- if (spans[i].className == "footnoteref") {
- var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
- href = href.match(/#.*/)[0]; // Because IE return full URL.
- n = refs[href];
- spans[i].innerHTML =
- "[<a href='#_footnote_" + n +
- "' title='View footnote' class='footnote'>" + n + "</a>]";
- }
- }
- }
-},
-
-install: function(toclevels) {
- var timerId;
-
- function reinstall() {
- asciidoc.footnotes();
- if (toclevels) {
- asciidoc.toc(toclevels);
- }
- }
-
- function reinstallAndRemoveTimer() {
- clearInterval(timerId);
- reinstall();
- }
-
- timerId = setInterval(reinstall, 500);
- if (document.addEventListener)
- document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
- else
- window.onload = reinstallAndRemoveTimer;
-}
-
-}
-asciidoc.install();
-/*]]>*/
-</script>
-</head>
-<body class="manpage">
-<div id="header">
-<h1>
-qdrouterd.conf(5) Manual Page
-</h1>
-<h2>NAME</h2>
-<div class="sectionbody">
+ <h2>NAME</h2>
<p>qdrouterd.conf -
configuration file for the dispatch router.
</p>
-</div>
-</div>
-<div id="content">
-<div class="sect1">
-<h2 id="_synopsis">SYNOPSIS</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>Provides the initial configuration when <em>qdrouterd(8)</em> starts. The configuration
-of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_description">DESCRIPTION</h2>
-<div class="sectionbody">
-<div class="paragraph"><p>The configuration file is made up of sections with this syntax:</p></div>
-<div class="listingblock">
-<div class="content">
+<h2><a name="_synopsis"></a>SYNOPSIS</h2>
+<p>Provides the initial configuration when <b>qdrouterd(8)</b> starts. The configuration
+of a running router can be modified using <b>qdmanage(8)</b>.</p>
+<h2><a name="_description"></a>DESCRIPTION</h2>
+<p>The configuration file is made up of sections with this syntax:</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>sectionName {
attributeName: attributeValue
attributeName: attributeValue
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>For example you can define a router using the <em>router</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>For example you can define a router using the <b>router</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>router {
mode: standalone
id: Router.A
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a listener using the <em>listener</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>or define a listener using the <b>listener</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>listener {
host: 0.0.0.0
port: 20102
saslMechanisms: ANONYMOUS
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>or define a connector using the <em>connector</em> section</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>or define a connector using the <b>connector</b> section</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>connector {
role: inter-router
host: 0.0.0.0
@@ -906,12 +156,11 @@ of a running router can be modified using <em>qdmanage(8)</em>.</p></div>
saslMechanisms: ANONYMOUS
...
}</code></pre>
-</div></div>
-<div class="paragraph"><p>An <em>sslProfile</em> section with SSL credentials can be included in multiple <em>listener</em> or <em>connector</em> entities. Here’s an example, note
-how the <em>sslProfile</em> attribute of <em>listener</em> sections references the <em>name</em>
-attribute of <em>sslProfile</em> sections.</p></div>
-<div class="listingblock">
-<div class="content">
+</td></tr></table>
+<p>An <b>sslProfile</b> section with SSL credentials can be included in multiple <b>listener</b> or <b>connector</b> entities. Here’s an example, note
+how the <b>sslProfile</b> attribute of <b>listener</b> sections references the <b>name</b>
+attribute of <b>sslProfile</b> sections.</p>
+<table border="0" bgcolor="#e8e8e8" width="100%" cellpadding="10"><tr><td>
<pre><code>sslProfile {
name: my-ssl
certDb: ca-certificate-1.pem
@@ -925,1001 +174,952 @@ listener {
port: 20102
saslMechanisms: ANONYMOUS
}</code></pre>
-</div></div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_configuration_sections">Configuration Sections</h2>
-<div class="sectionbody">
-<div class="sect2">
-<h3 id="_sslprofile">sslProfile</h3>
-<div class="paragraph"><p>Attributes for setting TLS/SSL configuration for connections.</p></div>
-<div class="paragraph"><p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>certDb</em> (path)
+</td></tr></table>
+<h2><a name="_configuration_sections"></a>Configuration Sections</h2>
+<h3><a name="_sslprofile"></a>sslProfile</h3>
+<p>Attributes for setting TLS/SSL configuration for connections.</p>
+<p>Used by: <strong>listener</strong>, <strong>connector</strong>.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>certFile</em> (path)
+<dt>
+<b>certDb</b> (path)
</dt>
<dd>
<p>
- The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
+ The absolute path to the database that contains the public certificates of trusted certificate authorities (CA).
</p>
</dd>
-<dt class="hdlist1">
-<em>keyFile</em> (path)
+<dt>
+<b>certFile</b> (path)
</dt>
<dd>
<p>
- The absolute path to the file containing the PEM-formatted private key for the above certificate.
+ The absolute path to the file containing the PEM-formatted public certificate to be used on the local end of any connections using this profile.
</p>
</dd>
-<dt class="hdlist1">
-<em>passwordFile</em> (path)
+<dt>
+<b>keyFile</b> (path)
</dt>
<dd>
<p>
- If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
+ The absolute path to the file containing the PEM-formatted private key for the above certificate.
</p>
</dd>
-<dt class="hdlist1">
-<em>password</em> (string)
+<dt>
+<b>passwordFile</b> (path)
</dt>
<dd>
<p>
- An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <em>password</em> option. Don’t use both password and passwordFile in the same profile.
+ If the above private key is password protected, this is the absolute path to a file containing the password that unlocks the certificate key.
</p>
</dd>
-<dt class="hdlist1">
-<em>uidFormat</em> (string)
+<dt>
+<b>password</b> (string)
</dt>
<dd>
<p>
- A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <em>cou</em> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <em>o2</em> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <em>c</em>( ISO3166 two character country code), <em>s</em>(state or province), <em>l</em>(Locality; generally - city), <em>o</em>(Organization - Company Name), <em>u</em>(Organization Unit - typically certificate type or brand), <em>n</em>(CommonName - typically a user name for client certificates) and <em>1</em>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and
2 (sha256 certificate fingerprint) and 5 (sha512 certificate fingerprint).
+ An alternative to storing the password in a file referenced by passwordFile is to supply the password right here in the configuration file. This option can be used by supplying the password in the <b>password</b> option. Don’t use both password and passwordFile in the same profile.
</p>
</dd>
-<dt class="hdlist1">
-<em>displayNameFile</em> (string)
+<dt>
+<b>uidFormat</b> (string)
</dt>
<dd>
<p>
- The absolute path to the file containing the unique id to dispay name mapping
+ A list of x509 client certificate fields that will be used to build a string that will uniquely identify the client certificate owner. For e.g. a value of <b>cou</b> indicates that the uid will consist of c - common name concatenated with o - organization-company name concatenated with u - organization unit; or a value of <b>o2</b> indicates that the uid will consist of o (organization name) concatenated with 2 (the sha256 fingerprint of the entire certificate) . Allowed values can be any combination of <b>c</b>( ISO3166 two character country code), <b>s</b>(state or province), <b>l</b>(Locality; generally - city), <b>o</b>(Organization - Company Name), <b>u</b>(Organization Unit - typically certificate type or brand), <b>n</b>(CommonName - typically a user name for client certificates) and <b>1</b>(sha1 certificate fingerprint, as displayed in the fingerprints section when looking at a certificate with say a web browser is the hash of the entire certificate) and 2 (sha256 certifi
cate fingerprint) and 5 (sha512 certificate fingerprint).
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string)
+<dt>
+<b>displayNameFile</b> (string)
</dt>
<dd>
<p>
- name of the sslProfile
+ The absolute path to the file containing the unique id to dispay name mapping
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_container">container</h3>
-<div class="paragraph"><p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>containerName</em> (string)
+</dl>
+<h3><a name="_container"></a>container</h3>
+<p>(DEPRECATED)Attributes related to the AMQP container. This entity has been deprecated. Use the router entity instead.</p>
+<dl>
+<dt>
+<b>containerName</b> (string)
</dt>
<dd>
<p>
The name of the AMQP container. If not specified, the container name will be set to a value of the container’s choosing. The automatically assigned container name is not guaranteed to be persistent across restarts of the container.
</p>
</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
+<dt>
+<b>workerThreads</b> (integer, default=4)
</dt>
<dd>
<p>
The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
</p>
</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
+<dt>
+<b>debugDump</b> (path)
</dt>
<dd>
<p>
A file to dump debugging information that can’t be logged normally.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
+<dt>
+<b>saslConfigPath</b> (path)
</dt>
<dd>
<p>
Absolute path to the SASL configuration file.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string)
+<dt>
+<b>saslConfigName</b> (string)
</dt>
<dd>
<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+ Name of the SASL configuration. This string + <b>.conf</b> is the name of the configuration file.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_router">router</h3>
-<div class="paragraph"><p>Tracks peer routers and computes routes to destinations.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>routerId</em> (string)
+</dl>
+<h3><a name="_router"></a>router</h3>
+<p>Tracks peer routers and computes routes to destinations.</p>
+<dl>
+<dt>
+<b>routerId</b> (string)
</dt>
<dd>
<p>
(DEPRECATED) Router’s unique identity. This attribute has been deprecated. Use id instead
</p>
</dd>
-<dt class="hdlist1">
-<em>id</em> (string)
+<dt>
+<b>id</b> (string)
</dt>
<dd>
<p>
Router’s unique identity. One of id or routerId is required. The router will fail to start without id or routerId
</p>
</dd>
-<dt class="hdlist1">
-<em>mode</em> (One of [<em>standalone</em>, <em>interior</em>], default=<em>standalone</em>)
+<dt>
+<b>mode</b> (One of [<b>standalone</b>, <b>interior</b>], default=<b>standalone</b>)
</dt>
<dd>
<p>
In standalone mode, the router operates as a single component. It does not participate in the routing protocol and therefore will not cooperate with other routers. In interior mode, the router operates in cooperation with other interior routers in an interconnected network.
</p>
</dd>
-<dt class="hdlist1">
-<em>helloInterval</em> (integer, default=1)
+<dt>
+<b>helloInterval</b> (integer, default=1)
</dt>
<dd>
<p>
Interval in seconds between HELLO messages sent to neighbor routers.
</p>
</dd>
-<dt class="hdlist1">
-<em>helloMaxAge</em> (integer, default=3)
+<dt>
+<b>helloMaxAge</b> (integer, default=3)
</dt>
<dd>
<p>
Time in seconds after which a neighbor is declared lost if no HELLO is received.
</p>
</dd>
-<dt class="hdlist1">
-<em>raInterval</em> (integer, default=30)
+<dt>
+<b>raInterval</b> (integer, default=30)
</dt>
<dd>
<p>
Interval in seconds between Router-Advertisements sent to all routers in a stable network.
</p>
</dd>
-<dt class="hdlist1">
-<em>raIntervalFlux</em> (integer, default=4)
+<dt>
+<b>raIntervalFlux</b> (integer, default=4)
</dt>
<dd>
<p>
Interval in seconds between Router-Advertisements sent to all routers during topology fluctuations.
</p>
</dd>
-<dt class="hdlist1">
-<em>remoteLsMaxAge</em> (integer, default=60)
+<dt>
+<b>remoteLsMaxAge</b> (integer, default=60)
</dt>
<dd>
<p>
Time in seconds after which link state is declared stale if no RA is received.
</p>
</dd>
-<dt class="hdlist1">
-<em>mobileAddrMaxAge</em> (integer, default=60)
+<dt>
+<b>mobileAddrMaxAge</b> (integer, default=60)
</dt>
<dd>
<p>
(DEPRECATED) This value is no longer used in the router.
</p>
</dd>
-<dt class="hdlist1">
-<em>workerThreads</em> (integer, default=4)
+<dt>
+<b>workerThreads</b> (integer, default=4)
</dt>
<dd>
<p>
The number of threads that will be created to process message traffic and other application work (timers, non-amqp file descriptors, etc.) .
</p>
</dd>
-<dt class="hdlist1">
-<em>debugDump</em> (path)
+<dt>
+<b>debugDump</b> (path)
</dt>
<dd>
<p>
A file to dump debugging information that can’t be logged normally.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigPath</em> (path)
+<dt>
+<b>saslConfigPath</b> (path)
</dt>
<dd>
<p>
Absolute path to the SASL configuration file.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslConfigName</em> (string, default=<em>qdrouterd</em>)
+<dt>
+<b>saslConfigName</b> (string, default=<b>qdrouterd</b>)
</dt>
<dd>
<p>
- Name of the SASL configuration. This string + <em>.conf</em> is the name of the configuration file.
+ Name of the SASL configuration. This string + <b>.conf</b> is the name of the configuration file.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_listener">listener</h3>
-<div class="paragraph"><p>Listens for incoming connections to the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
+</dl>
+<h3><a name="_listener"></a>listener</h3>
+<p>Listens for incoming connections to the router.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- Space separated list of accepted SASL authentication mechanisms.
+ Unique name optionally assigned by user. Can be changed.
</p>
</dd>
-<dt class="hdlist1">
-<em>authenticatePeer</em> (boolean)
+<dt>
+<b>host</b> (string)
</dt>
<dd>
<p>
- yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
+ IP address: ipv4 or ipv6 literal or a host name
</p>
</dd>
-<dt class="hdlist1">
-<em>requireEncryption</em> (boolean)
+<dt>
+<b>port</b> (string)
</dt>
<dd>
<p>
- yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
+ Port number or symbolic service name.
</p>
</dd>
-<dt class="hdlist1">
-<em>requireSsl</em> (boolean)
+<dt>
+<b>protocolFamily</b> (One of [<b>IPv4</b>, <b>IPv6</b>])
</dt>
<dd>
<p>
- yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
+ [<b>IPv4</b>, <b>IPv6</b>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
</p>
</dd>
-<dt class="hdlist1">
-<em>trustedCerts</em> (path)
+<dt>
+<b>role</b> (One of [<b>normal</b>, <b>inter-router</b>, <b>route-container</b>, <b>on-demand</b>])
</dt>
<dd>
<p>
- This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=16384)
+<dt>
+<b>cost</b> (integer)
</dt>
<dd>
<p>
- Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+ For the <b>inter-router</b> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
</p>
</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
+<dt>
+<b>sslProfile</b> (string)
</dt>
<dd>
<p>
- The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>requirePeerAuth</em> (boolean)
+<dt>
+<b>saslMechanisms</b> (string)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+ Space separated list of accepted SASL authentication mechanisms.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowUnsecured</em> (boolean)
+<dt>
+<b>authenticatePeer</b> (boolean)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
+ yes: Require the peer’s identity to be authenticated; no: Do not require any authentication.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowNoSasl</em> (boolean)
+<dt>
+<b>requireEncryption</b> (boolean)
</dt>
<dd>
<p>
- (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
+ yes: Require the connection to the peer to be encrypted; no: Permit non-encrypted communication with the peer
</p>
</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+<dt>
+<b>requireSsl</b> (boolean)
</dt>
<dd>
<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+ yes: Require the use of SSL or TLS on the connection; no: Allow clients to connect without SSL or TLS.
</p>
</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
+<dt>
+<b>trustedCerts</b> (path)
</dt>
<dd>
<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+ This optional setting can be used to reduce the set of available CAs for client authentication. If used, this setting must provide the absolute path to a PEM file that contains the trusted certificates.
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
+<dt>
+<b>maxFrameSize</b> (integer, default=16384)
</dt>
<dd>
<p>
- Unique name optionally assigned by user. Can be changed.
+ Defaults to 16384. If specified, it is the maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
</p>
</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
+<dt>
+<b>idleTimeoutSeconds</b> (integer, default=16)
</dt>
<dd>
<p>
- IP address: ipv4 or ipv6 literal or a host name
+ The idle timeout, in seconds, for connections through this listener. If no frames are received on the connection for this time interval, the connection shall be closed.
</p>
</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
+<dt>
+<b>requirePeerAuth</b> (boolean)
</dt>
<dd>
<p>
- Port number or symbolic service name.
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+<dt>
+<b>allowUnsecured</b> (boolean)
</dt>
<dd>
<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+ (DEPRECATED) This attribute is now controlled by the requireEncryption attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
+<dt>
+<b>allowNoSasl</b> (boolean)
</dt>
<dd>
<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+ (DEPRECATED) This attribute is now controlled by the authenticatePeer attribute.
</p>
</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
+<dt>
+<b>stripAnnotations</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+ [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
</p>
</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
+<dt>
+<b>linkCapacity</b> (integer)
</dt>
<dd>
<p>
- name of the sslProfile
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_connector">connector</h3>
-<div class="paragraph"><p>Establishes an outgoing connection from the router.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>saslMechanisms</em> (string)
+</dl>
+<h3><a name="_connector"></a>connector</h3>
+<p>Establishes an outgoing connection from the router.</p>
+<dl>
+<dt>
+<b>name</b> (string)
</dt>
<dd>
<p>
- Space separated list of accepted SASL authentication mechanisms.
+ Unique name optionally assigned by user. Can be changed.
</p>
</dd>
-<dt class="hdlist1">
-<em>allowRedirect</em> (boolean, default=True)
+<dt>
+<b>host</b> (string)
</dt>
<dd>
<p>
- Allow the peer to redirect this connection to another address.
+ IP address: ipv4 or ipv6 literal or a host name
</p>
</dd>
-<dt class="hdlist1">
-<em>maxFrameSize</em> (integer, default=65536)
+<dt>
+<b>port</b> (string)
</dt>
<dd>
<p>
- Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
+ Port number or symbolic service name.
</p>
</dd>
-<dt class="hdlist1">
-<em>idleTimeoutSeconds</em> (integer, default=16)
+<dt>
+<b>protocolFamily</b> (One of [<b>IPv4</b>, <b>IPv6</b>])
</dt>
<dd>
<p>
- The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
+ [<b>IPv4</b>, <b>IPv6</b>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
</p>
</dd>
-<dt class="hdlist1">
-<em>stripAnnotations</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>], default=<em>both</em>)
+<dt>
+<b>role</b> (One of [<b>normal</b>, <b>inter-router</b>, <b>route-container</b>, <b>on-demand</b>])
</dt>
<dd>
<p>
- [<em>in</em>, <em>out</em>, <em>both</em>, <em>no</em>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
+ The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
</p>
</dd>
-<dt class="hdlist1">
-<em>linkCapacity</em> (integer)
+<dt>
+<b>cost</b> (integer)
</dt>
<dd>
<p>
- The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
+ For the <b>inter-router</b> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
</p>
</dd>
-<dt class="hdlist1">
-<em>verifyHostName</em> (boolean, default=True)
+<dt>
+<b>sslProfile</b> (string)
</dt>
<dd>
<p>
- yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
+ name of the sslProfile
</p>
</dd>
-<dt class="hdlist1">
-<em>saslUsername</em> (string)
+<dt>
+<b>saslMechanisms</b> (string)
</dt>
<dd>
<p>
- The user name that the connector is using to connect to a peer.
+ Space separated list of accepted SASL authentication mechanisms.
</p>
</dd>
-<dt class="hdlist1">
-<em>saslPassword</em> (string)
+<dt>
+<b>allowRedirect</b> (boolean, default=True)
</dt>
<dd>
<p>
- The password that the connector is using to connect to a peer.
+ Allow the peer to redirect this connection to another address.
</p>
</dd>
-<dt class="hdlist1">
-<em>name</em> (string, unique)
+<dt>
+<b>maxFrameSize</b> (integer, default=65536)
</dt>
<dd>
<p>
- Unique name optionally assigned by user. Can be changed.
+ Maximum frame size in octets that will be used in the connection-open negotiation with a connected peer. The frame size is the largest contiguous set of uninterrupted data that can be sent for a message delivery over the connection. Interleaving of messages on different links is done at frame granularity.
</p>
</dd>
-<dt class="hdlist1">
-<em>host</em> (string)
+<dt>
+<b>idleTimeoutSeconds</b> (integer, default=16)
</dt>
<dd>
<p>
- IP address: ipv4 or ipv6 literal or a host name
+ The idle timeout, in seconds, for connections through this connector. If no frames are received on the connection for this time interval, the connection shall be closed.
</p>
</dd>
-<dt class="hdlist1">
-<em>port</em> (string)
+<dt>
+<b>stripAnnotations</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- Port number or symbolic service name.
+ [<b>in</b>, <b>out</b>, <b>both</b>, <b>no</b>] in: Strip the dispatch router specific annotations only on ingress; out: Strip the dispatch router specific annotations only on egress; both: Strip the dispatch router specific annotations on both ingress and egress; no - do not strip dispatch router specific annotations
</p>
</dd>
-<dt class="hdlist1">
-<em>protocolFamily</em> (One of [<em>IPv4</em>, <em>IPv6</em>])
+<dt>
+<b>linkCapacity</b> (integer)
</dt>
<dd>
<p>
- [<em>IPv4</em>, <em>IPv6</em>] IPv4: Internet Protocol version 4; IPv6: Internet Protocol version 6. If not specified, the protocol family will be automatically determined from the address.
+ The capacity of links within this connection, in terms of message deliveries. The capacity is the number of messages that can be in-flight concurrently for each link.
</p>
</dd>
-<dt class="hdlist1">
-<em>role</em> (One of [<em>normal</em>, <em>inter-router</em>, <em>route-container</em>, <em>on-demand</em>])
+<dt>
+<b>verifyHostName</b> (boolean, default=True)
</dt>
<dd>
<p>
- The role of an established connection. In the normal role, the connection is assumed to be used for AMQP clients that are doing normal message delivery over the connection. In the inter-router role, the connection is assumed to be to another router in the network. Inter-router discovery and routing protocols can only be used over inter-router connections. route-container role can be used for router-container connections, for example, a router-broker connection. on-demand role has been deprecated.
+ yes: Ensures that when initiating a connection (as a client) the host name in the URL to which this connector connects to matches the host name in the digital certificate that the peer sends back as part of the SSL connection; no: Does not perform host name verification
</p>
</dd>
-<dt class="hdlist1">
-<em>cost</em> (integer)
+<dt>
+<b>saslUsername</b> (string)
</dt>
<dd>
<p>
- For the <em>inter-router</em> role only. This value assigns a cost metric to the inter-router connection. The default (and minimum) value is one. Higher values represent higher costs. The cost is used to influence the routing algorithm as it attempts to use the path with the lowest total cost from ingress to egress.
+ The user name that the connector is using to connect to a peer.
</p>
</dd>
-<dt class="hdlist1">
-<em>sslProfile</em> (string)
+<dt>
+<b>saslPassword</b> (string)
</dt>
<dd>
<p>
- name of the sslProfile
+ The password that the connector is using to connect to a peer.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_log">log</h3>
-<div class="paragraph"><p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>module</em> (One of [<em>ROUTER</em>, <em>ROUTER_CORE</em>, <em>ROUTER_HELLO</em>, <em>ROUTER_LS</em>, <em>ROUTER_MA</em>, <em>MESSAGE</em>, <em>SERVER</em>, <em>AGENT</em>, <em>CONTAINER</em>, <em>ERROR</em>, <em>POLICY</em>, <em>DEFAULT</em>], required)
+</dl>
+<h3><a name="_log"></a>log</h3>
+<p>Configure logging for a particular module. You can use the <code>UPDATE</code> operation to change log settings while the router is running.</p>
+<dl>
+<dt>
+<b>module</b> (One of [<b>ROUTER</b>, <b>ROUTER_CORE</b>, <b>ROUTER_HELLO</b>, <b>ROUTER_LS</b>, <b>ROUTER_MA</b>, <b>MESSAGE</b>, <b>SERVER</b>, <b>AGENT</b>, <b>CONTAINER</b>, <b>ERROR</b>, <b>POLICY</b>, <b>DEFAULT</b>], required)
</dt>
<dd>
<p>
- Module to configure. The special module <em>DEFAULT</em> specifies defaults for all modules.
+ Module to configure. The special module <b>DEFAULT</b> specifies defaults for all modules.
</p>
</dd>
-<dt class="hdlist1">
-<em>enable</em> (string, default=<em>default</em>, required)
+<dt>
+<b>enable</b> (string)
</dt>
<dd>
<p>
- Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <em>+</em> to enable that level and above. For example <em>trace,debug,warning+</em> means enable trace, debug, warning, error and critical. The value <em>none</em> means disable logging for the module. The value <em>default</em> means use the value from the DEFAULT module.
+ Levels are: trace, debug, info, notice, warning, error, critical. The enable string is a comma-separated list of levels. A level may have a trailing <b>+</b> to enable that level and above. For example <b>trace,debug,warning+</b> means enable trace, debug, warning, error and critical. The value <b>none</b> means disable logging for the module.
</p>
</dd>
-<dt class="hdlist1">
-<em>timestamp</em> (boolean)
+<dt>
+<b>timestamp</b> (boolean)
</dt>
<dd>
<p>
Include timestamp in log messages.
</p>
</dd>
-<dt class="hdlist1">
-<em>source</em> (boolean)
+<dt>
+<b>source</b> (boolean)
</dt>
<dd>
<p>
Include source file and line number in log messages.
</p>
</dd>
-<dt class="hdlist1">
-<em>output</em> (string)
+<dt>
+<b>output</b> (string)
</dt>
<dd>
<p>
- Where to send log messages. Can be <em>stderr</em>, <em>syslog</em> or a file name.
+ Where to send log messages. Can be <b>stderr</b>, <b>stdout</b>, <b>syslog</b> or a file name.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_fixedaddress">fixedAddress</h3>
-<div class="paragraph"><p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_fixedaddress"></a>fixedAddress</h3>
+<p>(DEPRECATED) Establishes treatment for addresses starting with a prefix. This entity has been deprecated. Use address instead</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
- The address prefix (always starting with <em>/</em>).
+ The address prefix (always starting with <b>/</b>).
</p>
</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
+<dt>
+<b>phase</b> (integer)
</dt>
<dd>
<p>
The phase of a multi-hop address passing through one or more waypoints.
</p>
</dd>
-<dt class="hdlist1">
-<em>fanout</em> (One of [<em>multiple</em>, <em>single</em>], default=<em>multiple</em>)
+<dt>
+<b>fanout</b> (One of [<b>multiple</b>, <b>single</b>], default=<b>multiple</b>)
</dt>
<dd>
<p>
- One of <em>multiple</em> or <em>single</em>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
+ One of <b>multiple</b> or <b>single</b>. Multiple fanout is a non-competing pattern. If there are multiple consumers using the same address, each consumer will receive its own copy of every message sent to the address. Single fanout is a competing pattern where each message is sent to only one consumer.
</p>
</dd>
-<dt class="hdlist1">
-<em>bias</em> (One of [<em>closest</em>, <em>spread</em>], default=<em>closest</em>)
+<dt>
+<b>bias</b> (One of [<b>closest</b>, <b>spread</b>], default=<b>closest</b>)
</dt>
<dd>
<p>
- Only if fanout is single. One of <em>closest</em> or <em>spread</em>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
+ Only if fanout is single. One of <b>closest</b> or <b>spread</b>. Closest bias means that messages to an address will always be delivered to the closest (lowest cost) subscribed consumer. Spread bias will distribute the messages across subscribers in an approximately even manner.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_waypoint">waypoint</h3>
-<div class="paragraph"><p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>address</em> (string, required)
+</dl>
+<h3><a name="_waypoint"></a>waypoint</h3>
+<p>(DEPRECATED) A remote node that messages for an address pass through. This entity has been deprecated. Use autoLink instead</p>
+<dl>
+<dt>
+<b>address</b> (string, required)
</dt>
<dd>
<p>
The AMQP address of the waypoint.
</p>
</dd>
-<dt class="hdlist1">
-<em>connector</em> (string, required)
+<dt>
+<b>connector</b> (string, required)
</dt>
<dd>
<p>
The name of the on-demand connector used to reach the waypoint’s container.
</p>
</dd>
-<dt class="hdlist1">
-<em>inPhase</em> (integer, default=-1)
+<dt>
+<b>inPhase</b> (integer, default=-1)
</dt>
<dd>
<p>
- The phase of the address as it is routed <em>to</em> the waypoint.
+ The phase of the address as it is routed <b>to</b> the waypoint.
</p>
</dd>
-<dt class="hdlist1">
-<em>outPhase</em> (integer, default=-1)
+<dt>
+<b>outPhase</b> (integer, default=-1)
</dt>
<dd>
<p>
- The phase of the address as it is routed <em>from</em> the waypoint.
+ The phase of the address as it is routed <b>from</b> the waypoint.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroutepattern">linkRoutePattern</h3>
-<div class="paragraph"><p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_linkroutepattern"></a>linkRoutePattern</h3>
+<p>(DEPRECATED) An address pattern to match against link sources and targets to cause the router to link-route the attach across the network to a remote node. This entity has been deprecated. Use linkRoute instead</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
- An address prefix to match against target and source addresses. This pattern must be of the form <em><text>.<text1>.<textN></em> or <em><text></em> or <em><text>.</em> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <em>org.apache</em> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
+ An address prefix to match against target and source addresses. This pattern must be of the form <b><text>.<text1>.<textN></b> or <b><text></b> or <b><text>.</b> and matches any address that contains that prefix. For example, if the prefix is set to org.apache (or org.apache.), any address that has the prefix <b>org.apache</b> (like org.apache.dev) will match. Note that a prefix must not start with a (.), can end in a (.) and can contain zero or more dots (.). Any characters between the dots are simply treated as part of the address
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>, <em>both</em>], default=<em>both</em>)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>, <b>both</b>], default=<b>both</b>)
</dt>
<dd>
<p>
- Link direction for match: <em>in</em> matches only links inbound to the client; <em>out</em> matches only links outbound from the client; <em>both</em> matches any link.
+ Link direction for match: <b>in</b> matches only links inbound to the client; <b>out</b> matches only links outbound from the client; <b>both</b> matches any link.
</p>
</dd>
-<dt class="hdlist1">
-<em>connector</em> (string)
+<dt>
+<b>connector</b> (string)
</dt>
<dd>
<p>
The name of the on-demand connector used to reach the target node’s container. If this value is not provided, it means that the target container is expected to be connected to a different router in the network. This prevents links to a link-routable address from being misinterpreted as message-routing links when there is no route to a valid destination available.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_address">address</h3>
-<div class="paragraph"><p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_address"></a>address</h3>
+<p>Entity type for address configuration. This is used to configure the treatment of message-routed deliveries within a particular address-space. The configuration controls distribution and address phasing.</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
The address prefix for the configured settings
</p>
</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>multicast</em>, <em>closest</em>, <em>balanced</em>], default=<em>balanced</em>)
+<dt>
+<b>distribution</b> (One of [<b>multicast</b>, <b>closest</b>, <b>balanced</b>], default=<b>balanced</b>)
</dt>
<dd>
<p>
Treatment of traffic associated with the address
</p>
</dd>
-<dt class="hdlist1">
-<em>waypoint</em> (boolean)
+<dt>
+<b>waypoint</b> (boolean)
</dt>
<dd>
<p>
Designates this address space as being used for waypoints. This will cause the proper address-phasing to be used.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressPhase</em> (integer)
+<dt>
+<b>ingressPhase</b> (integer)
</dt>
<dd>
<p>
Advanced - Override the ingress phase for this address
</p>
</dd>
-<dt class="hdlist1">
-<em>egressPhase</em> (integer)
+<dt>
+<b>egressPhase</b> (integer)
</dt>
<dd>
<p>
Advanced - Override the egress phase for this address
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_linkroute">linkRoute</h3>
-<div class="paragraph"><p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>prefix</em> (string, required)
+</dl>
+<h3><a name="_linkroute"></a>linkRoute</h3>
+<p>Entity type for link-route configuration. This is used to identify remote containers that shall be destinations for routed link-attaches. The link-routing configuration applies to an addressing space defined by a prefix.</p>
+<dl>
+<dt>
+<b>prefix</b> (string, required)
</dt>
<dd>
<p>
The address prefix for the configured settings
</p>
</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
+<dt>
+<b>containerId</b> (string)
</dt>
<dd>
<p>
ContainerID for the target container
</p>
</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
+<dt>
+<b>connection</b> (string)
</dt>
<dd>
<p>
The name from a connector or listener
</p>
</dd>
-<dt class="hdlist1">
-<em>distribution</em> (One of [<em>linkBalanced</em>], default=<em>linkBalanced</em>)
+<dt>
+<b>distribution</b> (One of [<b>linkBalanced</b>], default=<b>linkBalanced</b>)
</dt>
<dd>
<p>
Treatment of traffic associated with the address
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>], required)
</dt>
<dd>
<p>
- The permitted direction of links: <em>in</em> means client senders; <em>out</em> means client receivers
+ The permitted direction of links: <b>in</b> means client senders; <b>out</b> means client receivers
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_autolink">autoLink</h3>
-<div class="paragraph"><p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>addr</em> (string, required)
+</dl>
+<h3><a name="_autolink"></a>autoLink</h3>
+<p>Entity type for configuring auto-links. Auto-links are links whose lifecycle is managed by the router. These are typically used to attach to waypoints on remote containers (brokers, etc.).</p>
+<dl>
+<dt>
+<b>addr</b> (string, required)
</dt>
<dd>
<p>
The address of the provisioned object
</p>
</dd>
-<dt class="hdlist1">
-<em>dir</em> (One of [<em>in</em>, <em>out</em>], required)
+<dt>
+<b>dir</b> (One of [<b>in</b>, <b>out</b>], required)
</dt>
<dd>
<p>
The direction of the link to be created. In means into the router, out means out of the router.
</p>
</dd>
-<dt class="hdlist1">
-<em>phase</em> (integer)
+<dt>
+<b>phase</b> (integer)
</dt>
<dd>
<p>
- The address phase for this link. Defaults to <em>0</em> for <em>out</em> links and <em>1</em> for <em>in</em> links.
+ The address phase for this link. Defaults to <b>0</b> for <b>out</b> links and <b>1</b> for <b>in</b> links.
</p>
</dd>
-<dt class="hdlist1">
-<em>containerId</em> (string)
+<dt>
+<b>containerId</b> (string)
</dt>
<dd>
<p>
ContainerID for the target container
</p>
</dd>
-<dt class="hdlist1">
-<em>connection</em> (string)
+<dt>
+<b>connection</b> (string)
</dt>
<dd>
<p>
The name from a connector or listener
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_console">console</h3>
-<div class="paragraph"><p>Start a websocket/tcp proxy and http file server to serve the web console</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>listener</em> (string)
+</dl>
+<h3><a name="_console"></a>console</h3>
+<p>Start a websocket/tcp proxy and http file server to serve the web console</p>
+<dl>
+<dt>
+<b>listener</b> (string)
</dt>
<dd>
<p>
The name of the listener to send the proxied tcp traffic to.
</p>
</dd>
-<dt class="hdlist1">
-<em>wsport</em> (integer, default=5673)
+<dt>
+<b>wsport</b> (integer, default=5673)
</dt>
<dd>
<p>
port on which to listen for websocket traffic
</p>
</dd>
-<dt class="hdlist1">
-<em>proxy</em> (string)
+<dt>
+<b>proxy</b> (string)
</dt>
<dd>
<p>
The full path to the proxy program to run.
</p>
</dd>
-<dt class="hdlist1">
-<em>home</em> (string)
+<dt>
+<b>home</b> (string)
</dt>
<dd>
<p>
The full path to the html/css/js files for the console.
</p>
</dd>
-<dt class="hdlist1">
-<em>args</em> (string)
+<dt>
+<b>args</b> (string)
</dt>
<dd>
<p>
Optional args to pass the proxy program for logging, authentication, etc.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policy">policy</h3>
-<div class="paragraph"><p>Defines global connection limit</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maximumConnections</em> (integer)
+</dl>
+<h3><a name="_policy"></a>policy</h3>
+<p>Defines global connection limit</p>
+<dl>
+<dt>
+<b>maximumConnections</b> (integer)
</dt>
<dd>
<p>
Global maximum number of concurrent client connections allowed. Zero implies no limit. This limit is always enforced even if no other policy settings have been defined.
</p>
</dd>
-<dt class="hdlist1">
-<em>enableAccessRules</em> (boolean)
+<dt>
+<b>enableAccessRules</b> (boolean)
</dt>
<dd>
<p>
Enable user rule set processing and connection denial.
</p>
</dd>
-<dt class="hdlist1">
-<em>policyFolder</em> (path)
+<dt>
+<b>policyFolder</b> (path)
</dt>
<dd>
<p>
The absolute path to a folder that holds policyRuleset definition .json files. For a small system the rulesets may all be defined in this file. At a larger scale it is better to have the policy files in their own folder and to have none of the rulesets defined here. All rulesets in all .json files in this folder are processed.
</p>
</dd>
-<dt class="hdlist1">
-<em>defaultApplication</em> (string)
+<dt>
+<b>defaultApplication</b> (string)
</dt>
<dd>
<p>
Application policyRuleset to use for connections with no open.hostname or a hostname that does not match any existing policy. For users that don’t wish to use open.hostname or any multi-tennancy feature, this default policy can be the only policy in effect for the network.
</p>
</dd>
-<dt class="hdlist1">
-<em>defaultApplicationEnabled</em> (boolean)
+<dt>
+<b>defaultApplicationEnabled</b> (boolean)
</dt>
<dd>
<p>
Enable defaultApplication policy fallback logic.
</p>
</dd>
-</dl></div>
-</div>
-<div class="sect2">
-<h3 id="_policyruleset">policyRuleset</h3>
-<div class="paragraph"><p>Per application definition of the locations from which users may connect and the groups to which users belong.</p></div>
-<div class="dlist"><dl>
-<dt class="hdlist1">
-<em>maxConnections</em> (integer)
+</dl>
+<h3><a name="_policyruleset"></a>policyRuleset</h3>
+<p>Per application definition of the locations from which users may connect and the groups to which users belong.</p>
+<dl>
+<dt>
+<b>maxConnections</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxConnPerUser</em> (integer)
+<dt>
+<b>maxConnPerUser</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed for any single user. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>maxConnPerHost</em> (integer)
+<dt>
+<b>maxConnPerHost</b> (integer)
</dt>
<dd>
<p>
Maximum number of concurrent client connections allowed for any remote host. Zero implies no limit.
</p>
</dd>
-<dt class="hdlist1">
-<em>userGroups</em> (map)
+<dt>
+<b>userGroups</b> (map)
</dt>
<dd>
<p>
- A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed <em>restricted</em>. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.
+ A map where each key is a user group name and the corresponding value is a CSV string naming the users in that group. Users who are assigned to one or more groups are deemed <b>restricted</b>. Restricted users are subject to connection ingress policy and are assigned policy settings based on the assigned user groups. Unrestricted users may be allowed or denied. If unrestricted users are allowed to connect then they are assigned to user group default.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressHostGroups</em> (map)
+<dt>
+<b>ingressHostGroups</b> (map)
</dt>
<dd>
<p>
- A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address <em>*</em> represents any host address.
+ A map where each key is an ingress host group name and the corresponding value is a CSV string naming the IP addresses or address ranges in that group. IP addresses may be FQDN strings or numeric IPv4 or IPv6 host addresses. A host range is two host addresses of the same address family separated with a hyphen. The wildcard host address <b>*</b> represents any host address.
</p>
</dd>
-<dt class="hdlist1">
-<em>ingressPolicies</em> (map)
+<dt>
+<b>ingressPolicies</b> (map)
</dt>
<dd>
<p>
A map where each key is a user group name and the corresponding value is a CSV string naming the ingress host group names that restrict the ingress host for the user group. Users who are members of the user group are allowed to connect only from a host in one of the named ingress host groups.
</p>
</dd>
-<dt class="hdlist1">
-<em>connectionAllowDefault</em> (boolean)
+<dt>
+<b>connectionAllowDefault</b> (boolean)
</dt>
<dd>
<p>
- Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <em>default</em> user group and receive <em>default</em> settings.
+ Unrestricted users, those who are not members of a defined user group, are allowed to connect to this application. Unrestricted users are assigned to the <b>default</b> user group and receive <b>default</b> settings.
</p>
</dd>
-<dt class="hdlist1">
-<em>settings</em> (map)
+<dt>
+<b>settings</b> (map)
</dt>
<dd>
<p>
A map where each key is a user group name and the value is a map of the corresponding settings for that group.
</p>
</dd>
-</dl></div>
-</div>
-</div>
-</div>
-<div class="sect1">
-<h2 id="_see_also">SEE ALSO</h2>
-<div class="sectionbody">
-<div class="paragraph"><p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p></div>
-<div class="paragraph"><p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p></div>
-</div>
-</div>
-</div>
-<div id="footnotes"><hr /></div>
-<div id="footer">
-<div id="footer-text">
-Last updated 2016-06-23 12:42:34 EDT
-</div>
-</div>
-</body>
-</html>
+</dl>
+<h2><a name="_see_also"></a>SEE ALSO</h2>
+<p><strong>qdrouterd(8)</strong>, <strong>qdmanage(8)</strong></p>
+<p><a href="http://qpid.apache.org/components/dispatch-router">http://qpid.apache.org/components/dispatch-router</a></p>
<hr/>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org