Thanks for the quick reply.<div><br></div><div>So, is there anyways to achieve asynchronous acknowledgment of data?</div><div>Again, I also wanted to know if there is a way to replicate data, to increase the system's availability.</div>
<div><br></div><div>So that, if a node1 running RabbitMQ goes down, a slave comes up and works like a master, so that all the queues and data on node1, are still accessible?</div><div><br></div><div>Thanks,</div><div>Vivek</div>
<div><br><div><br><br><div class="gmail_quote">On Mon, Aug 16, 2010 at 6:29 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@rabbitmq.com">matthew@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On Mon, Aug 16, 2010 at 06:27:33PM +0530, vivek agarwal wrote:<br>
> Am I correct on this?<br>
<br>
</div>You are.<br>
<div class="im"><br>
> If so, is there any way or future plan to acknowledge<br>
> a message, by just the delivery tag, or some other tag, which does not needs<br>
> to know of which channel it was received from?<br>
<br>
</div>Nope. Delivery tags are scoped within channels. This is as defined by<br>
the AMQP spec.<br>
<font color="#888888"><br>
Matthew<br>
</font></blockquote></div><br></div></div>