[
https://issues.apache.org/jira/browse/DISPATCH-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Ross updated DISPATCH-34:
-----------------------------
Description:
Goal: Place a network of Routers between a client and a broker such that the
transfer of messages between the client and broker occurs normally and no code
changes are needed in the client or broker.
This feature enhances Dispatch Router such that the transfer of a message with
an address is divided into multiple "legs" with "waypoints" in between. For
example, a message may be produced, routed to a broker queue (the waypoint),
then later dequeued from the queue and routed to a consumer. In this example,
the address is always the same (i.e. the name of the queue), but the routing is
divided into two distinct paths, each with its own distinct semantics.
This feature generalizes the notion of leg (called phase) and waypoint so
multi-phase paths can be configured. There is no reason that a waypoint need
be limited to a broker or queue. It is simply a pass-through endpoint that
takes ownership of a message for the time it holds the message.
was:
Goal: Place a network of Routers between a client and a broker such that the
transfer of messages between the client and broker occurs normally and no code
changes are needed in the client or broker.
This feature enhances Dispatch Router such that the transfer of a message with
an address is divided into multiple "legs" with "waypoints" in between. For
example, a message may be produced, routed to a broker queue (the waypoint),
then later dequeued from the queue and routed to a consumer. In this example,
the address is always the same (i.e. the name of the queue), but the routing is
divided into two distinct paths, each with its own distinct semantics.
This feature generalizes the notion of leg (called phase) and waypoint so
multi-phase paths can be configured. There is not reason that a waypoint need
be limited to a broker or queue. It is simply a pass-through endpoint that
takes ownership of a message for the time it holds the message.
> Multi-Leg Addressing for Broker Integration
> -------------------------------------------
>
> Key: DISPATCH-34
> URL: https://issues.apache.org/jira/browse/DISPATCH-34
> Project: Qpid Dispatch
> Issue Type: New Feature
> Components: Router Node
> Affects Versions: 0.2
> Reporter: Ted Ross
> Assignee: Ted Ross
> Fix For: 0.3
>
>
> Goal: Place a network of Routers between a client and a broker such that the
> transfer of messages between the client and broker occurs normally and no
> code changes are needed in the client or broker.
> This feature enhances Dispatch Router such that the transfer of a message
> with an address is divided into multiple "legs" with "waypoints" in between.
> For example, a message may be produced, routed to a broker queue (the
> waypoint), then later dequeued from the queue and routed to a consumer. In
> this example, the address is always the same (i.e. the name of the queue),
> but the routing is divided into two distinct paths, each with its own
> distinct semantics.
> This feature generalizes the notion of leg (called phase) and waypoint so
> multi-phase paths can be configured. There is no reason that a waypoint need
> be limited to a broker or queue. It is simply a pass-through endpoint that
> takes ownership of a message for the time it holds the message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
