No subject

exclusive queues, is that correct? I've tried creating a named,
durable queue for all consumers to read from, but in this case the
message can only be consumed once.

Is there something I'm missing?

Thank you.

On Thu, Mar 3, 2011 at 22:07, Michael Bridgen <mikeb at rabbitmq.com> wrote:
> Fabio,
>
> Aces, glad to hear it's working for you thus far.
>
> On this:
>
>> Just a final question: the previous README file on github said
>> something about including the plugin on the main RabbitMQ code, but I
>> figured this had been written some time ago because it mentioned
>> version 1.7.1. Is this still in your (and RabbitMQ developers) plans?
>> Best regards.
>
> =A0-- I was referring to the exchange plugin mechanism overall, on which =
I was
> finishing (largely other people's!) work at the time. =A0That mechanism h=
as
> been in mainstream rabbitmq since then, and has changed a bit, but is pre=
tty
> stable.
>
> The Last Value Caching exchange will likely stay a plugin for the
> foreseeable future, rather than being baked into rabbitmq-server. =A0But =
if
> you follow this list you'll know this is not the last word ..
>
> Michael
>
>>> Oh. =A0Looks like github's upload and download system is totally broken=
.
>>> (I've
>>> now tried to upload it a few times).
>>>
>>> I've attached the ez so it can be stopped by mail filters instead.
>>
>> Hi Michael.
>> Sorry for the extra trouble.
>>
>> I've now rebooted my RabbitMQ server and run a few basic tests and
>> everything seems to be working as expected. Thank you again for all
>> your help and your work on the plugin. I'll keep building my test
>> scenarios and I'll let you know if something else comes up.
>>
>> Just a final question: the previous README file on github said
>> something about including the plugin on the main RabbitMQ code, but I
>> figured this had been written some time ago because it mentioned
>> version 1.7.1. Is this still in your (and RabbitMQ developers) plans?
>> Best regards.
>
>