qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carl Trieloff (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Resolved: (QPID-1595) Queue example: Multi-subscriber example using TTL and ACQUIRE_MODE_NOT_ACQUIRE
Date Mon, 09 Feb 2009 14:20:59 GMT

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

Carl Trieloff resolved QPID-1595.

    Resolution: Fixed

Committed revision 742515.

> Queue example: Multi-subscriber example using TTL and ACQUIRE_MODE_NOT_ACQUIRE
> ------------------------------------------------------------------------------
>                 Key: QPID-1595
>                 URL: https://issues.apache.org/jira/browse/QPID-1595
>             Project: Qpid
>          Issue Type: Improvement
>          Components: Qpid Examples
>    Affects Versions: M4
>            Reporter: William Henry
>         Attachments: Makefile.am, queues_demo.tar.gz
> Currently the examples tend to focus on the different types of exchanges.
> The attached files demonstrate an example that focuses more on queue configurations.
> Using a amq:topic exchange several topic based queues are declared with specific topic
bindings. These are the same bindings as used in the normal pub/sub example.
> The queues are declared as non-exclusive so that they can be shared b y multiple consumers
> The topic publisher publishes messages  to the amq:topic exchange with a TTL properties
set so that the messages will time out after a certain point and will not remain on the queue.
I.e. they have a Time-to-live and therefore the messages are out of date and irrelevant after
that TTL. (at some point we should address this on the consumer side and let the consumer
decide the TTL).
> The topic_listener subscribes to the queues with ACQUIRE_MODE_NOT_ACQUIRE. i.e. the listners
are browsing the messages and therefore leaving them on the queue.
> This example is similar to how some financial institutions may want to share information
on shared queues but the information only has relevance for a certain amount of time.
> I'd like to write up a description of this use case with code on the site somewhere.
 Where is appropriate? FAQ? Elsewhere? It would be useful to provide several consumer side
patterns of queue configuration etc. 
> Also should I also develop python, java,etc. examples of the same?
> Hmmm where to I attach the files?  I'll create first and then attach.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org

View raw message