[
https://issues.apache.org/jira/browse/QPID-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Henry updated QPID-1595:
--------------------------------
Attachment: queues_demo.tar.gz
This is a newer version of the demo. The changes I made are:
I changed the demo to be more financial services in nature. It now handles
ticker price data and market data.
The ticker price data is TTL and uses shared queues where the messages will
time out after a certain period.
The market data is using LVQs. Each listener declares its own LVQ(s).
Therefore I added LVQ to the demo to compliment the TTL example.
The publisher publishes both ticker price (with a TTL) and market data to a
amq:topic exchange.
declare_queues declares the non-exclusive (shared) queues for the ticker price
data.
The listener declares LVQs and subscribes to both those LVQs and the ticker
based queues.
The listener just prints all the data to std out.
> 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: 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 (subscribers).
> 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:[email protected]
