Would a durable subscriber (a la JMS) work? Not sure of the c++ api to
recreate this. That would retain messages received on the exchange
since first registration of the client.
Another potential option may be a 'ring LVQ topic' - one that holds
the last n values which would be sent to a new joiner. Again, not sure
if current qpid binding semantics allow this.
Cheers,
Andrew
On 31 Mar 2009, at 18:23, Shan Wang wrote:
Hi All,
According to the document, normally a listener of a publish/subscribe
kind of exchange can only receive messages after it begins running. Is
there any way to let the listeners receive all the messages ever
sent by
producer?
Basically what I need is to have multiple listeners subscribe to the
same queue and each receive exact the same messages sent by the
producer. It does seem to be possible using QPID.
Thanks & Regards,
Shan
The information contained in this email is strictly confidential and
for the use of the addressee only, unless otherwise indicated. If
you are not the intended recipient, please do not read, copy, use or
disclose to others this message or any attachment. Please also
notify the sender by replying to this email or by telephone (+44
(0)20 7896 0011) and then delete the email and any copies of it.
Opinions, conclusions (etc.) that do not relate to the official
business of this company shall be understood as neither given nor
endorsed by it. IG Index plc is a company registered in England and
Wales under number 01190902. VAT registration number 761 2978 07.
Registered Office: Friars House, 157-168 Blackfriars Road, London
SE1 8EZ. Authorised and regulated by the Financial Services
Authority. FSA Register number 114059.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
