Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Wed, 30 Nov 2011 16:01:40 +0000 (UTC)
From: "Hiram Chirino (Commented) (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: 
 <691154362.26441.1322668900944.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <564717188.24678.1322627380787.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (APLO-92) Support temporary destinations which
 can only be consumed by the connection which creates them
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/APLO-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160111#comment-13160111 ] 

Hiram Chirino commented on APLO-92:
-----------------------------------

With the way this is implemented, you don't really need support for the 'auto-delete' header on the subscribe frame.
                
> Support temporary destinations which can only be consumed by the connection which creates them
> ----------------------------------------------------------------------------------------------
>
>                 Key: APLO-92
>                 URL: https://issues.apache.org/jira/browse/APLO-92
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>          Components: apollo-broker, apollo-stomp
>    Affects Versions: 1.0-beta5
>            Reporter: Hiram Chirino
>            Assignee: Hiram Chirino
>             Fix For: 1.0-beta6
>
>
> Temporary destinations are typically used to receive response messages in
> a request/response messaging exchange.  A temporary destination can only
> be consumed by a subscription created on the connection which is associated
> with the temporary destination.  Once the connection is closed, all associated
> temporary destinations are removed. Temporary destinations are prefixed with:
> * `/temp-queue/` - For temporary queues.  Has the same delivery semantics as queues.
> * `/temp-topic/` - For temporary topics.  It has the same delivery semantics of topics.
> In a request/response scenario, you would first subscribe to the temporary topic:
>     SUBSCRIBE
>     id:mysub
>     destination:/temp-queue/example
>     
>     ^@
> Then you would send a request with the reply-to header set to the temporary destination. 
> Example:
>     SEND
>     destination:/queue/PO.REQUEST
>     reply-to:/temp-queue/example
>     PO145
>     ^@
> The consumer receiving the request will receive a message similar to:
>     MESSAGE
>     subscription:foo
>     reply-to:/queue/temp.default.23.example
>     destination:/queue/PO.REQUEST
>     reply-to:/temp-queue/example
>     
>     PO145
> Notice that the reply-to` header value is updated from a temporary destination
> name to normal destination name.  The subscription servicing he requests should respond
> to the updated destination value (`/queue/temp.default.23.example` in the example above).
> Temporary destination names actually map to normal queues and topics. They just have
> a `temp.<broker_id>.<connection_id>.` prefix.  Any destination which starts with
> `temp.` has a security policy which only allows the connection which created it
> to subscribe from it.  These destinations are also auto deleted once the connection
> is closed.
> Provides a better fix for APLO-86 and removes support for the 'temp:true' header on the subscribe frame.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira