No subject

o<br>
be easier to query for unconsumed messages, or query a common error queue<b=
r>
which is written to by the remote client, when things go amiss.<br>
<br>
But, should there be a network interruption between the time a client<br>
collects the message from Central, and starts the execution of instructions=
<br>
it contains, the Central Que would fail to get an ACK, or possible error<br=
>
message from the client. This could result in a lack of synchronicity<br>
between reality as understood by the remote client consumer, and the<br>
accounting and reporting mechanisms at Central.<br>
<br>
Hopefully I have conveyed more than my own confusion about this project.<br=
>
<br>
Thanks !<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
--<br>
View this message in context: <a href=3D"http://old.nabble.com/Architecture=
-Question%3A-2-Brokers%2C-or-Not-2-Brokers---tp33189279p33190235.html" targ=
et=3D"_blank">http://old.nabble.com/Architecture-Question%3A-2-Brokers%2C-o=
r-Not-2-Brokers---tp33189279p33190235.html</a><br>


</font></span><div class=3D"HOEnZb"><div class=3D"h5">Sent from the RabbitM=
Q mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href=3D"mailto:rabbitmq-discuss at lists.rabbitmq.com">rabbitmq-discuss at lis=
ts.rabbitmq.com</a><br>
<a href=3D"https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-dis=
cuss" target=3D"_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo=
/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>

--f46d044303f092459e04b73895a4--