Getting ready for the 0.4 release of Dispatch Router

[Ted Ross <tr...@redhat.com>]

Once the Proton 0.9 release is completed, we plan to put up a release 
candidate for Dispatch 0.4.

Dispatch 0.4 has a couple of important new features as well as a set of 
bug fixes:

   - Link-attach routing
   - Redesign of the route-computation engine
   - Improvements to the management agent

Link Attach Routing
===================

Link-attach routing is a form of message routing that occurs when links 
are attached, not when message deliveries arrive (both flavors of 
routing are now available).

This feature allows an AMQP endpoint to establish an AMQP link to a 
remote endpoint (typically a broker or server) through the network of 
routers.  Link segments are effectively chained across the network from 
endpoint node to endpoint node.  It is conceptually similar to setting 
up a virtual circuit across a telecom network.  This has some 
interesting benefits:

   - Client isolation:  Messaging clients can be restricted to only
     connect to the router that is local to their location.  Once
     connected locally, they can establish communication (senders and
     receivers) with brokered queues in different locations.

   - Broker virtualization:  The router network can be configured to
     expose only a subset of the resources on a particular broker.
     This is a building block for providing isolated, multi-tennant
     access to brokers that don't necessarily have multi-tennancy
     capability themselves.

Redesigned Router Engine
========================

The redesign was done to address a number of problems with network 
stability and to improve the time-to-stability after changes in topology 
(i.e. router failures, new routers added, etc).

The router engine in 0.4 is far more stable (settles on a correct and 
consistent topology after a change) and stabilizes far more quickly than 
it did in 0.3.

Management Agent Improvements
=============================

The management agent now has a feature by which a client can query the 
agent's detailed management schema.  The schema is returned either as a 
json document or as an AMQP-encoded message body.

-Ted

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