So mandatory or not, the channel doesn't release the publisher until it's routed the message? So if a node crash were to occur while a message was being routed the publisher could assume the message was lost because the the publisher would still be waiting to be released when they lost connection?<div>
<br></div><div>My understanding previously was that when you publish it's fire-and-forget while the routing occurs...you're instantly released while the routing is in process.</div><div><br></div><div>-J </div><div>
<br><div class="gmail_quote">On Wed, Mar 23, 2011 at 6:36 AM, 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 Tue, Mar 22, 2011 at 06:06:43PM -0600, Jason J. W. Williams wrote:<br>
> So there really are no guarantees as to the contents of an exchange on<br>
> failure of a node. You can just be sure that the exchange will exist as<br>
> expected on the other nodes.<br>
<br>
</div>It's wrong to think of an exchange as having "contents". An exchange<br>
really just names a collection of routing rules (i.e. bindings). At no<br>
point is a message ever held "in" an exchange.<br>
<br>
But otherwise, yes, exchanges just exist on every node, but the bindings<br>
of that exchange will vary dynamically with the actions of clients and<br>
the failure or restoration of nodes within the cluster.<br>
<div><div></div><div class="h5"><br>
Matthew<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>