[rabbitmq-discuss] building system architecture

Tue Jul 17 19:48:06 BST 2012

> Again it's not clear to me what you mean here. It seems to me that a
> one-queue-per-client solution with publisher confirms would suffice in your
> case. You have strong guarantees against the loss of messages, and you can ack
> the messages once you've finished building. If rabbit fails, you know that the
> messages are persisted and thus they won't be lost. If the consumer fails, the
> messages pending acks will be redelivered to the next consumer (with a
> `redeliver' flag to indicate that the messages was sent before).
>
>
I've done one queue by client. While client is free - it sends special 
messages every 10 seconds, server will receive it and send tasks to 
client if possible. Server sends special immideate message to every 
online client every 10 seconds too. When client dies, its queue will be 
deleted (thanks to queue declaration flags) and message will be reterned 
to server, server will now the client is dead. It looks workable, but 
it's not implemented yet. I'll keep you informed :)