[rabbitmq-discuss] Help defining appropriate queue model
alexis at rabbitmq.com
Wed Mar 2 17:12:21 GMT 2011
On Wed, Mar 2, 2011 at 4:58 PM, Alister Morton
<Alister.Morton at tradition.com> wrote:
>> I'd tentatively suggest that you may be talking more about a cache
>> than message queue.
> Or failing that, perhaps a bit like the "real time record" model, such as used for financial data, where a consumer gets the last published update for a topic. IIRC the guys at Rabbit HQ did some work on an exchange which persists the last update to a topic - what became of that? This would fit the problem definition quite well, I think.
Yes, though I think that plugin won't work with RabbitMQ 2.3.1. Maybe
it could be revived...
> The information herein may have been obtained from various sources. Any opinion expressed may be that of the sender only, is subject to change without notice and should be independently evaluated. Nothing herein constitutes investment advice or an offer, or solicitation of an offer, to buy or sell any financial product. Any data consists of purely indicative prices and should not be relied upon to revalue any commercial positions held by any recipient. Tradition makes no warranty that the data represent or indicates prices at which transactions may be or have been made by any Tradition Group company. To the maximum extent of the law, Tradition accepts no responsibility for, and cannot and does not warrant the integrity, accuracy, quality, completeness, merchantability or suitability for a particular purpose or requirement of the information or data, even if arising out of the negligence of Tradition or otherwise. Tradition accepts no liability for any direct, indirect or other consequential loss arising out of any use of the information contained in this document or any omission from it. This communication is directed at Eligible Counterparties and Professional Clients as defined by the FSA. It is not for distribution to nor should it be relied upon by Private Clients. It is not intended for distribution to, or use by any person or entity in any jurisdiction or country where such distribution or use would be contrary to any applicable law or regulation. Please note that, for business or compliance reasons, we may monitor and read emails sent or received using our servers or equipment. Tradition (UK) Ltd (937647; FSA 139200), Tradition Financial Services Ltd (1046064; FSA 147543), TFS Derivatives Ltd (4051930; FSA 197244), Tradition London Clearing Ltd (3633863; FSA 190632) and TFS-ICAP Ltd (4025995; FSA 206018) registered in England at Beaufort House, 15 St Botolph Street, London EC3A 7QX; authorised and regulated by the Financial Services Authority. VAT No: GB 365 4639 27 except TFS-ICAP GB 766 0854 05.
More information about the rabbitmq-discuss