Return-Path: X-Original-To: apmail-qpid-commits-archive@www.apache.org Delivered-To: apmail-qpid-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 19FCD196C4 for ; Tue, 5 Apr 2016 17:01:25 +0000 (UTC) Received: (qmail 83259 invoked by uid 500); 5 Apr 2016 17:01:25 -0000 Delivered-To: apmail-qpid-commits-archive@qpid.apache.org Received: (qmail 83229 invoked by uid 500); 5 Apr 2016 17:01:25 -0000 Mailing-List: contact commits-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 83218 invoked by uid 99); 5 Apr 2016 17:01:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Apr 2016 17:01:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6F5F5C0227 for ; Tue, 5 Apr 2016 17:01:24 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.799 X-Spam-Level: * X-Spam-Status: No, score=1.799 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 3pLK7jb0Sq7Q for ; Tue, 5 Apr 2016 17:01:13 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8B80A5F645 for ; Tue, 5 Apr 2016 17:01:12 +0000 (UTC) Received: from svn01-us-west.apache.org (svn.apache.org [10.41.0.6]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 96857E0112 for ; Tue, 5 Apr 2016 17:01:11 +0000 (UTC) Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 707503A022C for ; Tue, 5 Apr 2016 17:01:11 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1737854 [1/4] - in /qpid/site: docs/releases/qpid-dispatch-master/ docs/releases/qpid-dispatch-master/book/ docs/releases/qpid-dispatch-master/man/ input/releases/qpid-dispatch-master/ input/releases/qpid-dispatch-master/book/ input/releas... Date: Tue, 05 Apr 2016 17:01:11 -0000 To: commits@qpid.apache.org From: tross@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160405170111.707503A022C@svn01-us-west.apache.org> Author: tross Date: Tue Apr 5 17:01:10 2016 New Revision: 1737854 URL: http://svn.apache.org/viewvc?rev=1737854&view=rev Log: Updated master Dispatch docs Added: qpid/site/docs/releases/qpid-dispatch-master/book/auto_links.html qpid/site/docs/releases/qpid-dispatch-master/book/console.html qpid/site/docs/releases/qpid-dispatch-master/book/console_installation.html qpid/site/docs/releases/qpid-dispatch-master/book/console_operation.html qpid/site/docs/releases/qpid-dispatch-master/book/console_overview.html qpid/site/input/releases/qpid-dispatch-master/book/auto_links.html.in qpid/site/input/releases/qpid-dispatch-master/book/console.html.in qpid/site/input/releases/qpid-dispatch-master/book/console_installation.html.in qpid/site/input/releases/qpid-dispatch-master/book/console_operation.html.in qpid/site/input/releases/qpid-dispatch-master/book/console_overview.html.in Modified: qpid/site/docs/releases/qpid-dispatch-master/book/addressing.html qpid/site/docs/releases/qpid-dispatch-master/book/amqp-mapping.html qpid/site/docs/releases/qpid-dispatch-master/book/basic_usage.html qpid/site/docs/releases/qpid-dispatch-master/book/book.html qpid/site/docs/releases/qpid-dispatch-master/book/client_compatibility.html qpid/site/docs/releases/qpid-dispatch-master/book/default_config.html qpid/site/docs/releases/qpid-dispatch-master/book/introduction.html qpid/site/docs/releases/qpid-dispatch-master/book/link_routing.html qpid/site/docs/releases/qpid-dispatch-master/book/schema.html qpid/site/docs/releases/qpid-dispatch-master/book/technical_details.html qpid/site/docs/releases/qpid-dispatch-master/book/tools.html qpid/site/docs/releases/qpid-dispatch-master/book/using.html qpid/site/docs/releases/qpid-dispatch-master/index.html qpid/site/docs/releases/qpid-dispatch-master/man/qdmanage.html qpid/site/docs/releases/qpid-dispatch-master/man/qdrouterd.conf.html qpid/site/docs/releases/qpid-dispatch-master/man/qdrouterd.html qpid/site/docs/releases/qpid-dispatch-master/man/qdstat.html qpid/site/input/releases/qpid-dispatch-master/book/addressing.html.in qpid/site/input/releases/qpid-dispatch-master/book/amqp-mapping.html.in qpid/site/input/releases/qpid-dispatch-master/book/basic_usage.html.in qpid/site/input/releases/qpid-dispatch-master/book/book.html.in qpid/site/input/releases/qpid-dispatch-master/book/client_compatibility.html.in qpid/site/input/releases/qpid-dispatch-master/book/default_config.html.in qpid/site/input/releases/qpid-dispatch-master/book/introduction.html.in qpid/site/input/releases/qpid-dispatch-master/book/link_routing.html.in qpid/site/input/releases/qpid-dispatch-master/book/schema.html.in qpid/site/input/releases/qpid-dispatch-master/book/technical_details.html.in qpid/site/input/releases/qpid-dispatch-master/book/tools.html.in qpid/site/input/releases/qpid-dispatch-master/book/using.html.in qpid/site/input/releases/qpid-dispatch-master/index.md qpid/site/input/releases/qpid-dispatch-master/man/qdmanage.html.in qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.conf.html.in qpid/site/input/releases/qpid-dispatch-master/man/qdrouterd.html.in qpid/site/input/releases/qpid-dispatch-master/man/qdstat.html.in qpid/site/python/generate.py Modified: qpid/site/docs/releases/qpid-dispatch-master/book/addressing.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/addressing.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/addressing.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/addressing.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

3.2. Addressing.

Modified: qpid/site/docs/releases/qpid-dispatch-master/book/amqp-mapping.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/amqp-mapping.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/amqp-mapping.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/amqp-mapping.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

3.3. AMQP Mapping.

@@ -163,11 +164,10 @@ properties. A router may append, remove, annotation field depending on the policy in place for routing the message. -x-opt-qd.class -string -Message class. This is used to allow the router to -provide separate paths for different classes of -traffic. +x-opt-qd.phase +integer +The address-phase, if not zero, for messages flowing +between routers. @@ -188,7 +188,13 @@ traffic. qd.router This capability is added to sources and targets that are used for -inter-router message exchange. +inter-router message exchange. This capability denotes a link used for +router-control messages flowing between routers. + +qd.router-data +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. @@ -238,14 +244,18 @@ Dispatch Router.

endpoint. Messages using this address pattern shall not be routed over more than one link. -_topo/<area>/<router>/<addr> -An address that references an endpoint attached to a +_topo/0/<router>/<addr> +

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. +route the message to its destination.

+

The ‘0’ component immediately preceding the router-id +is a placeholder for an _area_ which may be used in +the future if area routing is implemented.

+ <addr> A mobile address. An address of this format represents @@ -262,8 +272,8 @@ addresses.

3.3.4.2. Supported Addresses.

--++ @@ -277,7 +287,7 @@ address would be used by an endpoint tha client/console/tool wishing to access management data from the attached container. - +
Address
_topo/0/Router.E/agent
_topo/0/Router.E/$management 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 Added: qpid/site/docs/releases/qpid-dispatch-master/book/auto_links.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/auto_links.html?rev=1737854&view=auto ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/auto_links.html (added) +++ qpid/site/docs/releases/qpid-dispatch-master/book/auto_links.html Tue Apr 5 17:01:10 2016 @@ -0,0 +1,349 @@ + + + + + 2.5. Indirect Waypoints and Auto-Links. - Apache Qpid™ + + + + + + + + + + + + + +
+ + + + + + +
+ + +
+ + + + + + + +
+ + + + +
+
+
+ + Modified: qpid/site/docs/releases/qpid-dispatch-master/book/basic_usage.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/basic_usage.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/basic_usage.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/basic_usage.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

2.3. Basic Usage and Examples.

@@ -127,32 +128,36 @@ with any other routers and only routes m endpoints.

If your router is running in stand-alone mode, qdstat -a will look like the following:

-
$ qdstat -a
+
$ qdstat -a
 Router Addresses
-  class   address          phase  in-proc  local  remote  in  out  thru  to-proc  from-proc
-  ===========================================================================================
-  local   $management             Y        0      0       0   0    0     0        0
-  mobile  $management      0      Y        0      0       1   0    0     1        0
-  local   temp.4Q3i01lWbs                  1      0       0   0    0     0        0
-
+ 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
-

Note that there are two known addresses. $management is the address of -the router’s embedded management agent. temp.4Q3i01lWbs is the temporary +

Note that there are a number of known addresses. $management is the address of +the router’s embedded management agent. temp.1GThUllfR7N+BDP is the temporary reply-to address of the qdstat client making requests to the agent.

If you change the mode to interior and restart the processs, the same command will yield additional addresses which are used for inter-router communication:

-
$ qdstat -a
+
$ qdstat -a
 Router Addresses
-  class   address          phase  in-proc  local  remote  in  out  thru  to-proc  from-proc
-  ===========================================================================================
-  local   $management             Y        0      0       0   0    0     0        0
-  mobile  $management      0      Y        0      0       1   0    0     1        0
-  local   qdhello                 Y        0      0       0   0    0     0        3
-  local   qdrouter                Y        0      0       0   0    0     0        1
-  local   qdrouter.ma             Y        0      0       0   0    0     0        0
-  local   temp.2ot2AWsnYz                  1      0       0   0    0     0        0
-
+ 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
@@ -164,25 +169,24 @@ attaches, the messages will be routed to

To illustrate a subscription on a stand-alone router, you can use the examples that are provided with Qpid Proton. Using the simple_recv.py example receiver:

-
$ python ./simple_recv.py -a 127.0.0.1/my-address
-
+
$ python ./simple_recv.py -a 127.0.0.1/my-address

This command creates a receiving link subscribed to the specified address. To verify the subscription:

-
$ qdstat -a
+
$ qdstat -a
 Router Addresses
-  class   address          phase  in-proc  local  remote  in  out  thru  to-proc  from-proc
-  ===========================================================================================
-  local   $management             Y        0      0       0   0    0     0        0
-  mobile  $management      0      Y        0      0       1   0    0     1        0
-  mobile  my-address       0               1      0       0   0    0     0        0
-  local   temp.JAgKj1+iB8                  1      0       0   0    0     0        0
-
+ 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

You can then, in a separate command window, run a sender to produce messages to that address:

-
$ python ./simple_send.py -a 127.0.0.1/my-address
-
+
$ python ./simple_send.py -a 127.0.0.1/my-address
@@ -193,7 +197,7 @@ take to get there. To illustrate this fe program (written in C++ against the qpid::messaging API) that queries the management agent of the attached router for a list of other known routers’ management addresses.

-
#include <qpid/messaging/Address.h>
+
#include <qpid/messaging/Address.h>
 #include <qpid/messaging/Connection.h>
 #include <qpid/messaging/Message.h>
 #include <qpid/messaging/Receiver.h>
@@ -207,33 +211,32 @@ using std::stringstream;
 using std::string;
 
 int main() {
-    const char* url = "amqp:tcp:127.0.0.1:5672";
-    std::string connectionOptions = "{protocol:amqp1.0}";
+    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");
+    Sender sender = session.createSender("mgmt");
 
     // create reply receiver and get the reply-to address
-    Receiver receiver = session.createReceiver("#");
+    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");
+    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;
+    std::cout << "Response: " << content << std::endl << std::endl;
 
     connection.close();
-}
-
+}

The equivalent program written in Python against the Proton Messenger API:

Modified: qpid/site/docs/releases/qpid-dispatch-master/book/book.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/book.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/book.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/book.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+ Modified: qpid/site/docs/releases/qpid-dispatch-master/book/client_compatibility.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/client_compatibility.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/client_compatibility.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/client_compatibility.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

3.1. Client Compatibility.

Added: qpid/site/docs/releases/qpid-dispatch-master/book/console.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/console.html?rev=1737854&view=auto ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/console.html (added) +++ qpid/site/docs/releases/qpid-dispatch-master/book/console.html Tue Apr 5 17:01:10 2016 @@ -0,0 +1,170 @@ + + + + + 4. Console. - Apache Qpid™ + + + + + + + + + + + + + +
+ + + + + + +
+ + +
+ + + + + + + +
+ + + + +
+
+
+ + Added: qpid/site/docs/releases/qpid-dispatch-master/book/console_installation.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/console_installation.html?rev=1737854&view=auto ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/console_installation.html (added) +++ qpid/site/docs/releases/qpid-dispatch-master/book/console_installation.html Tue Apr 5 17:01:10 2016 @@ -0,0 +1,192 @@ + + + + + 4.2. Console installation. - Apache Qpid™ + + + + + + + + + + + + + +
+ + + + + + +
+ + +
+ + + +
+

4.2. Console installation.

+
+

4.2.1. Prerequisites.

+

The following need to be installed before running a console:

+
    +
  • One or more dispatch routers. See the documentation for the dispatch router for help in starting a router network.
  • +
  • node.js This is needed to provide a proxy between the console’s websocket traffic and tcp.
  • +
  • A web server. This can be any server capable of serving static html/js/css/image files.
  • +
+

A nodejs proxy is distributed with proton. +To start the proton’s nodejs proxy:

+
cd ~/rh-qpid-proton/examples/javascript/messenger
+node proxy.js &
+
+

This will start the proxy listening to ws traffic on port 5673 and translating it to tcp on port 5672. +One of the routers in the network needs to have a listener configured on port 5672. That listener’s role should be ‘normal’. For example:

+
listener {
+   addr: 0.0.0.0
+   role: normal
+   port: amqp
+   saslMechanisms: ANONYMOUS
+}
+
+
+
+

4.2.2. The console files.

+

The files for the console are located under the console directory in +the source tree.:

+
app/
+bower_components/
+css/
+img/
+index.html
+lib/
+plugin/
+vendor.js
+
+
+
Copy these files to a directory under the the html or webapps directory of your web server. For example, for apache tomcat the files should be under webapps/dispatch. Then the console is available as::
+
http://localhost:8080/dispatch
+
+
+
+ + + +
+ + + + +
+
+
+ + Added: qpid/site/docs/releases/qpid-dispatch-master/book/console_operation.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/console_operation.html?rev=1737854&view=auto ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/console_operation.html (added) +++ qpid/site/docs/releases/qpid-dispatch-master/book/console_operation.html Tue Apr 5 17:01:10 2016 @@ -0,0 +1,185 @@ + + + + + 4.3. Console operation. - Apache Qpid™ + + + + + + + + + + + + + +
+ + + + + + +
+ + +
+ + + +
+

4.3. Console operation.

+
+

4.3.1. Logging in to a router network.

+

The console communicates to the router network using the proton javascript bindings. When run from a web page, the proton bindings use web sockets to send and receive commands. However, the dispatch router requires tcp. Therefore a web-sockets to tcp proxy is used.

+console_login.png +

Enter the address of a proxy that is connected to a router in the network.

+

User name and password are not used at this time.

+

The Autostart checkbox, when checked, will automatically log in with the previous host:port the next time you start the console.

+
+
+

4.3.2. Overview page.

+

On the overview page, aggregate information about routers, addresses, and connections is displayed.

+console_overview.png +
+
+

4.3.3. Topology page.

+

This page displays the router network in a graphical form showing how the routers are connected and information about the individual routers and links.

+console_topology.png +
+
+

4.3.4. Router entity details page.

+console_entity.png +

Displays detailed information about entities such as routers, links, addresses, memory.

+

Numeric attributes can be graphed by clicking on the graph icon.

+
+
+

4.3.5. Charts page.

+console_charts.png +

This page displays graphs of numeric values that are on the entity details page.

+
+
+

4.3.6. Schema page.

+console_schema.png +

This page displays the json schema that is used to manage the router network.

+
+
+ + + +
+ + + + +
+
+
+ + Added: qpid/site/docs/releases/qpid-dispatch-master/book/console_overview.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/console_overview.html?rev=1737854&view=auto ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/console_overview.html (added) +++ qpid/site/docs/releases/qpid-dispatch-master/book/console_overview.html Tue Apr 5 17:01:10 2016 @@ -0,0 +1,155 @@ + + + + + 4.1. Console overview. - Apache Qpid™ + + + + + + + + + + + + + +
+ + + + + + +
+ + +
+ + + +
+

4.1. Console overview.

+

The console is an HTML based web site that displays information about a qpid dispatch router network.

+

The console requires an HTML web server that can serve static html, javascript, style sheets, and images.

+

The current version of the is read-only. The ability to call management methods that change the running of the router network is planned for a future version of console.

+

The console only provides limited information about the clients that are attached to the router network and is therfore more appropriate for administrators needing to know the layout and health of the router network.

+
+ + + +
+ + + + +
+
+
+ + Modified: qpid/site/docs/releases/qpid-dispatch-master/book/default_config.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/default_config.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/default_config.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/default_config.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

2.1. Configuration.

Modified: qpid/site/docs/releases/qpid-dispatch-master/book/introduction.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/introduction.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/introduction.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/introduction.html Tue Apr 5 17:01:10 2016 @@ -115,6 +115,7 @@ https://github.com/apache/qpid-proton/bl
+

1. Introduction.

Modified: qpid/site/docs/releases/qpid-dispatch-master/book/link_routing.html URL: http://svn.apache.org/viewvc/qpid/site/docs/releases/qpid-dispatch-master/book/link_routing.html?rev=1737854&r1=1737853&r2=1737854&view=diff ============================================================================== --- qpid/site/docs/releases/qpid-dispatch-master/book/link_routing.html (original) +++ qpid/site/docs/releases/qpid-dispatch-master/book/link_routing.html Tue Apr 5 17:01:10 2016 @@ -115,10 +115,12 @@ https://github.com/apache/qpid-proton/bl
+