You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2014/01/30 22:12:09 UTC

[jira] [Updated] (APLO-326) Routable Network

     [ https://issues.apache.org/jira/browse/APLO-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hiram Chirino updated APLO-326:
-------------------------------

    Affects Version/s:     (was: wish-list)

> Routable Network
> ----------------
>
>                 Key: APLO-326
>                 URL: https://issues.apache.org/jira/browse/APLO-326
>             Project: ActiveMQ Apollo
>          Issue Type: Wish
>          Components: apollo-amqp, apollo-broker
>         Environment: Linux, Windows, Mac
>            Reporter: Jack Gibson
>             Fix For: wish-list
>
>
> Create a network of brokers via AMQP links such that a client can publish a message and have it routed to downstream brokers via the address in the AMQP header.
> Use case: local broker that a client interacts with and publishes a message to a destination that does not exist on that broker and the message is routed to the broker with that destination.  
> Use case 2: client creates a dedicated destination for responses (could be a temporary queue).  The client sends a message to a known destination the consumer of that destination can publish a response to the client's reply to even if the client is not on the same broker.
> Use case 3: a group of brokers that are "load balanced" clients can connect to any broker and publish/receive from destinations on the other brokers.  This would be used in a cloud/horizontal scaling environment.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)