<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1257">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.6619.12">
<TITLE>RE: [rabbitmq-discuss] A new exchange type</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Tony, our messages volumes aren�t large, so it was implemented simply.<BR>
RabbitMQ were used for pub/sub routing and scalable transportation of the messages:<BR>
Client application (publisher) calls remote Windows communication service (WCF). It does some validations, logs message to db and publishes to rabbitmq clients. When (subscriber) client starts, it calls WCF service for �last message� list.<BR>
Simple but works for our case. If reasonable we may replace �GetLastMessages� service after new exchange will be created.<BR>
<BR>
-----Original Message-----<BR>
From: Tony Garnock-Jones [<A HREF="mailto:tonyg@lshift.net">mailto:tonyg@lshift.net</A>]<BR>
Sent: Tr 2009.01.28 13:43<BR>
To: Andrius Norkaitis<BR>
Cc: Alister Morton; rabbitmq-discuss@lists.rabbitmq.com<BR>
Subject: Re: [rabbitmq-discuss] A new exchange type<BR>
<BR>
Andrius Norkaitis wrote:<BR>
> Currently we are using custom implementation of second the case. When a<BR>
> user starts listening to newly declared query, he also asks �service�<BR>
> for the last messages that haven�t timeout.<BR>
<BR>
That's a useful stopgap solution. I know a bunch of people that would be<BR>
interested in such a piece of software, until a proper last-value-cache<BR>
is implemented: is it something you'd be willing to share?<BR>
<BR>
Regards,<BR>
Tony<BR>
--<BR>
[][][] Tony Garnock-Jones | Mob: +44 (0)7905 974 211<BR>
[][] LShift Ltd | Tel: +44 (0)20 7729 7060<BR>
[] [] <A HREF="http://www.lshift.net/">http://www.lshift.net/</A> | Email: tonyg@lshift.net<BR>
<BR>
<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>