[rabbitmq-discuss] ewbie question - need modified fanaout/publish/subscribe behavior

[scott taggart]

Matthias,

Thanks for the response.  Short story is that I have not crossed the 
bridge of "forgetting" about messages in my message queuing server.  I 
will figure that out, eventually.  It may not be a problem because the 
message Q server only has to run a limited amount of time...

Hey, unrelated question - I cannot get the python pika queue_declare 
method to accept an empty queue name so that the q name is 
auto-generated.  I looked for issues with this online and could not find 
any.  The python demo 3 sample, for example,  at the rabbitmq site shows 
queue_declare as taking no queue parameter yet the current 0.9.6 
function demands a queue parameter. Thoughts?

Thanks,

Scott


On 11/8/2012 8:05 AM, Matthias Radestock wrote:
> Scott,
>
> On 08/11/12 15:57, scott taggart wrote:
>> As I research and better understand AMQP better, I learn that messages
>> are never queued in an exchange - they are always routed to existing
>> queues or tossed.  Given my basic requirement that messages
>> be queued for as-yet non-existent queues, this seems not possible
>> directly with amqp/rabbitmq.
>
> Yes, that's basically correct. Though it's not too hard to be build 
> something along those lines on top of amqp/rabbitmq as long as you 
> don't care about certain edge cases.
>
> Btw, when in your hypothetical system can the server ever forget a 
> message? Never?
>
> Regards,
>
> Matthias.
>
>