Hi Ashwin,<br><br>Messages are not explicitly copied - Erlang's message-passing is used to distribute "copies" of each AMQP message to the queue processes it is destined for. Since Erlang terms are immutable, the underlying memory-management system is free to use whichever strategy works best. Sometimes that will be many pointers to a shared value; other times it will be separate copies. I don't know which strategy Erlang chooses at present: you will have to ask the Erlang mailing list or do some experiments of your own. Hope this helps!<br>
<br>Regards,<br> Tony<br><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 December 2012 01:40, Ashwin Raghav <span dir="ltr"><<a href="mailto:ashwinraghav@gmail.com" target="_blank">ashwinraghav@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi tony,<div>I had a questions about how(whether) rabbit internally copies a message from an exchange to a queue.</div>
<div>I have read the documentation that says "Exchanges copy messages to queues using rules called bindings".</div>
<div><br clear="all"><div>I was wondering whether this is a logical copy or an actual full-on copy. I ask because I was posed with a question recently on a project that I work on. Why are you physically copying the same message to so many queues? Would something like a reference count implementation with just a single copy of the message not suffice?</div>
<div><br></div><div>Kindly clarify.</div><span class="HOEnZb"><font color="#888888">-- <br>Regards,<br>Ashwin Raghav Mohan Ganesh<br clear="all"><br>-- <br>Tony Garnock-Jones<br><a href="mailto:tonygarnockjones@gmail.com" target="_blank">tonygarnockjones@gmail.com</a><br>
<a href="http://homepages.kcbbs.gen.nz/tonyg/" target="_blank">http://homepages.kcbbs.gen.nz/tonyg/</a><br>
<br>
</font></span></div></blockquote></div></div>