qpid-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tr...@apache.org
Subject svn commit: r1504615 - in /qpid/site: docs/components/dispatch/addressing.html docs/components/dispatch/index.html docs/components/index.html input/components/dispatch/addressing.md input/components/dispatch/index.md input/components/index.md
Date Thu, 18 Jul 2013 19:24:01 GMT
Author: tross
Date: Thu Jul 18 19:24:01 2013
New Revision: 1504615

URL: http://svn.apache.org/r1504615
Log:
QPID-5001 - Updates to the Dispatch pages

Modified:
    qpid/site/docs/components/dispatch/addressing.html
    qpid/site/docs/components/dispatch/index.html
    qpid/site/docs/components/index.html
    qpid/site/input/components/dispatch/addressing.md
    qpid/site/input/components/dispatch/index.md
    qpid/site/input/components/index.md

Modified: qpid/site/docs/components/dispatch/addressing.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch/addressing.html?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch/addressing.html (original)
+++ qpid/site/docs/components/dispatch/addressing.html Thu Jul 18 19:24:01 2013
@@ -21,7 +21,7 @@
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   <head>
-    <title>Qpid Dispatch Addressing - Apache Qpid&#153;</title>
+    <title>Dispatch Addressing - Apache Qpid&#153;</title>
     <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
     <link rel="stylesheet" href="http://qpid.apache.org/site.css" type="text/css"/>
     <link rel="stylesheet" href="http://qpid.apache.org/pygments.css" type="text/css"/>
@@ -46,8 +46,8 @@
         </ul>
       </div>
       <div id="middle">
-        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li><a
href="http://qpid.apache.org/components/dispatch/index.html">Qpid Dispatch Router</a></li><li>Qpid
Dispatch Addressing</li></ul>
-        <h1 id="qpid-dispatch-addressing">Qpid Dispatch Addressing</h1>
+        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li><a
href="http://qpid.apache.org/components/dispatch/index.html">Dispatch Router</a></li><li>Dispatch
Addressing</li></ul>
+        <h1 id="dispatch-addressing">Dispatch Addressing</h1>
 
 <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
@@ -55,6 +55,52 @@ protocol.  They can be used in a specifi
 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>
 
+<p>Addresses designate various kinds of entities in a messaging network:</p>
+
+<ul>
+<li>Endpoint processes that consume data or offer a service</li>
+<li>Topics that match multiple consumers to multiple producers</li>
+<li>Entities within a messaging broker:
+<ul>
+<li>Queues</li>
+<li>Durable Topics</li>
+<li>Exchanges</li>
+</ul></li>
+</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>
+
+<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>
+
+<p>Address semantics include the following considerations:</p>
+
+<ul>
+<li>Routing pattern (direct, multicast, balanced)</li>
+<li>Routing mechanism (message routed, link routed)</li>
+<li>Undeliverable action (drop, hold and retry, redirect)</li>
+<li>Reliability (N destinations, etc.)</li>
+</ul>
+
+<h2 id="routing-patterns">Routing patterns</h2>
+
+<p>Routing patterns constrain the paths that a message can take across a network.</p>
+
+<table>
+<tbody>
+<tr><td><em>Pattern</em></td><td><em>Description</em></td></tr>
+<tr><td><em>Direct</em></td><td>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.</td></tr>
+<tr><td><em>Multicast</em></td><td>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.</td></tr>
+<tr><td><em>Balanced</em></td><td>Balanced routing also
allows multiple consumers to use the same address.  In this case, messages (or links) 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.</td></tr>
+</tbody>
+</table>
+
 <h2 id="routing-mechanisms">Routing mechanisms</h2>
 
 <p>The fact that addresses can be used in different ways suggests that message

Modified: qpid/site/docs/components/dispatch/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/dispatch/index.html?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/docs/components/dispatch/index.html (original)
+++ qpid/site/docs/components/dispatch/index.html Thu Jul 18 19:24:01 2013
@@ -21,7 +21,7 @@
 -->
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
   <head>
-    <title>Qpid Dispatch Router - Apache Qpid&#153;</title>
+    <title>Dispatch Router - Apache Qpid&#153;</title>
     <meta http-equiv="X-UA-Compatible" content="IE=edge"/>
     <link rel="stylesheet" href="http://qpid.apache.org/site.css" type="text/css"/>
     <link rel="stylesheet" href="http://qpid.apache.org/pygments.css" type="text/css"/>
@@ -46,8 +46,8 @@
         </ul>
       </div>
       <div id="middle">
-        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li>Qpid
Dispatch Router</li></ul>
-        <h1 id="qpid-dispatch-router">Qpid Dispatch Router</h1>
+        <ul id="path-navigation"><li><a href="http://qpid.apache.org/components/index.html">Components</a></li><li>Dispatch
Router</li></ul>
+        <h1 id="dispatch-router">Dispatch Router</h1>
 
 <p>A lightweight message router, written in C and built on
 <a href="http://qpid.apache.org/proton/index.html">Qpid Proton</a>, that provides
flexible
@@ -64,6 +64,25 @@ and brokers.</p>
 </tbody>
 </table>
 
+<h2 id="overview">Overview</h2>
+
+<p>Dispatch Router is an AMQP router that provides advanced interconnect for AMQP.
+It is <em>not</em> a broker.  It will never assume ownership of a message.  It
will,
+however, propagate settlement and disposition across a network such that delivery
+guarantees are met.</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 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.</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>
+
 <h2 id="benefits">Benefits</h2>
 
 <ul>

Modified: qpid/site/docs/components/index.html
URL: http://svn.apache.org/viewvc/qpid/site/docs/components/index.html?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/docs/components/index.html (original)
+++ qpid/site/docs/components/index.html Thu Jul 18 19:24:01 2013
@@ -77,7 +77,7 @@ persistence, and manageability.</p>
 <li><a href="cpp-broker-tools/index.html">C++ broker command-line tools</a>
- Manage the C++ broker</li>
 <li><a href="java-broker/index.html">Java broker</a> - A pure-Java AMQP
message broker</li>
 <li><a href="qmf/index.html">QMF</a> - Management built on Qpid messaging</li>
-<li><a href="dispatch/index.html">Qpid Dispatch router</a> - An AMQP router
for scalable messaging interconnect</li>
+<li><a href="dispatch/index.html">Dispatch router</a> - An AMQP router
for scalable messaging interconnect</li>
 </ul>
 
 <h2 id="compatibility">Compatibility</h2>
@@ -90,7 +90,7 @@ persistence, and manageability.</p>
 <tr><td><a href="http://qpid.apache.org/components/cpp-broker/index.html">C++
broker</a></td><td>C++</td><td>Linux, Windows</td><td>1.0,
0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/cpp-broker-tools/index.html">C++
broker command-line tools</a></td><td>-</td><td>Linux</td><td>0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/java-broker/index.html">Java
broker</a></td><td>Java</td><td>JVM</td><td>1.0,
0-10, 0-91, 0-9, 0-8</td></tr>
-<tr><td><a href="dispatch/index.html">Qpid Dispatch router</a></td><td>C</td><td>Linux</td><td>1.0</td></tr>
+<tr><td><a href="dispatch/index.html">Dispatch router</a></td><td>C</td><td>Linux</td><td>1.0</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qpid-jca/index.html">Qpid
JCA</a></td><td>Java</td><td>JVM</td><td>0-10</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/qpid-jms/index.html">Qpid
JMS</a></td><td>Java</td><td>JVM</td><td>1.0, 0-10,
0-91, 0-9, 0-8</td></tr>
 <tr><td><a href="http://qpid.apache.org/components/messaging-api/index.html">Qpid
Messaging API</a></td><td>C++, Perl, Python, Ruby, .NET</td><td>Linux,
Windows</td><td>1.0, 0-10</td></tr>

Modified: qpid/site/input/components/dispatch/addressing.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch/addressing.md?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/input/components/dispatch/addressing.md (original)
+++ qpid/site/input/components/dispatch/addressing.md Thu Jul 18 19:24:01 2013
@@ -17,7 +17,7 @@
 ;; under the License.
 ;;
 
-# Qpid Dispatch Addressing
+# Dispatch Addressing
 
 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
@@ -25,6 +25,42 @@ protocol.  They can be used in a specifi
 fields of a message's properties.  They are also used during the creation of
 links in the `address` field of a `source` or a `target`.
 
+Addresses designate various kinds of entities in a messaging network:
+
+ - Endpoint processes that consume data or offer a service
+ - Topics that match multiple consumers to multiple producers
+ - Entities within a messaging broker:
+   - Queues
+   - Durable Topics
+   - Exchanges
+   
+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.
+
+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.
+
+Address semantics include the following considerations:
+
+ - Routing pattern (direct, multicast, balanced)
+ - Routing mechanism (message routed, link routed)
+ - Undeliverable action (drop, hold and retry, redirect)
+ - Reliability (N destinations, etc.)
+
+## Routing patterns
+
+Routing patterns constrain the paths that a message can take across a network.
+
+  || *Pattern* || *Description* ||
+  || *Direct* || 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. ||
+  || *Multicast* || 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.
||
+  || *Balanced* || Balanced routing also allows multiple consumers to use the same address.
 In this case, messages (or links) 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. ||
+
 ## Routing mechanisms
 
 The fact that addresses can be used in different ways suggests that message

Modified: qpid/site/input/components/dispatch/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/dispatch/index.md?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/input/components/dispatch/index.md (original)
+++ qpid/site/input/components/dispatch/index.md Thu Jul 18 19:24:01 2013
@@ -17,7 +17,7 @@
 ;; under the License.
 ;;
 
-# Qpid Dispatch Router
+# Dispatch Router
 
 A lightweight message router, written in C and built on
 [Qpid Proton](@site-url@/proton/index.html), that provides flexible
@@ -30,6 +30,25 @@ and brokers.
   || *Source location* ||  <http://svn.apache.org/repos/asf/qpid/trunk/qpid/extras/dispatch/>
||
   || *Issues* || [Open bugs](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+%3D+%22Bug%22+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22),
[Completed enhancements](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Closed%22%2C+%22Resolved%22%29+and+resolution+%3D+%22Fixed%22+and+component+%3D+%22Qpid+Dispatch%22),
[Requested enhancements](https://issues.apache.org/jira/issues/?jql=project+%3D+%22Qpid%22+and+issuetype+in+%28%22New+Feature%22%2C+%22Improvement%22%29+and+status+in+%28%22Open%22%2C+%22Reopened%22%2C+%22In+Progress%22%2C+%22Ready+To+Review%22%29+and+component+%3D+%22Qpid+Dispatch%22)
||
 
+## Overview
+
+Dispatch Router is an AMQP router that provides advanced interconnect for AMQP.
+It is *not* a broker.  It will never assume ownership of a message.  It will,
+however, propagate settlement and disposition across a network such that delivery
+guarantees are met.
+
+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.
+
+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.
+
 ## Benefits
 
  - Simplifies connectivity
@@ -56,4 +75,4 @@ and brokers.
 ;;find previous versions with our
 ;;[past releases](@site-url@/releases/index.html#past-releases).
 
-;; - [Deployment and Configuration Guide](@current-dispatch-release-url@/qpid-dispatch-deploy/book/index.html)
+;; - [Deployment and Configuration Guide](@current-dispatch-release-url@/dispatch-deploy/book/index.html)

Modified: qpid/site/input/components/index.md
URL: http://svn.apache.org/viewvc/qpid/site/input/components/index.md?rev=1504615&r1=1504614&r2=1504615&view=diff
==============================================================================
--- qpid/site/input/components/index.md (original)
+++ qpid/site/input/components/index.md Thu Jul 18 19:24:01 2013
@@ -44,7 +44,7 @@ persistence, and manageability.
  - [C++ broker command-line tools](cpp-broker-tools/index.html) - Manage the C++ broker
  - [Java broker](java-broker/index.html) - A pure-Java AMQP message broker
  - [QMF](qmf/index.html) - Management built on Qpid messaging
- - [Qpid Dispatch router](dispatch/index.html) - An AMQP router for scalable messaging interconnect
+ - [Dispatch router](dispatch/index.html) - An AMQP router for scalable messaging interconnect
  
 ## Compatibility
 
@@ -54,7 +54,7 @@ persistence, and manageability.
   || [C++ broker](@site-url@/components/cpp-broker/index.html) || C++ || Linux, Windows ||
1.0, 0-10 ||
   || [C++ broker command-line tools](@site-url@/components/cpp-broker-tools/index.html) ||
- || Linux || 0-10 ||
   || [Java broker](@site-url@/components/java-broker/index.html) || Java || JVM || 1.0, 0-10,
0-91, 0-9, 0-8 ||
-  || [Qpid Dispatch router](dispatch/index.html) || C || Linux || 1.0 ||
+  || [Dispatch router](dispatch/index.html) || C || Linux || 1.0 ||
   || [Qpid JCA](@site-url@/components/qpid-jca/index.html) || Java || JVM || 0-10 ||
   || [Qpid JMS](@site-url@/components/qpid-jms/index.html) || Java || JVM || 1.0, 0-10, 0-91,
0-9, 0-8 ||
   || [Qpid Messaging API](@site-url@/components/messaging-api/index.html) || C++, Perl, Python,
Ruby, .NET || Linux, Windows || 1.0, 0-10 ||



---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org
For additional commands, e-mail: commits-help@qpid.apache.org


Mime
View raw message