<div>Dear Steve,</div>
<div>�</div>
<div>Actually I am dealing with a distributed database (kind of), and I am doing things like�sending the same request to different shards, every shard processes it and replies to the sender, which will merge results. It is pretty much like a map reduce job.</div>
<div>�</div>
<div>I found out that routing offers�nice ways for handling this kind of request/response schemes (for example, I can send one request to one instance of�each shard of�my computing�grid with only one publish).</div>
<div>�</div>
<div>So I think you misunderstood my point, it is nothing like concatenating multiple response messaging, but like a more generic rpc.</div>
<div>�</div>
<div>John</div>
<div><br>�</div>
<div class="gmail_quote">2011/12/5 Steve Powell <span dir="ltr"><<a href="mailto:steve@rabbitmq.com">steve@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Dear John,<br><br>Our work was, in part, prompted by your questions. �Thank you.<br><br>I think we will be able to manage two of your three issues. �The 'multiple<br>
replies' scheme is tricky, and we do not intend to try this straight away.<br>There are many problems with it which could result in an ugly interface.<br>Is there any reason why a large reply would not be adequate?<br>
<br>Steve 'bun' Powell<br>
<div class="im">----------some more definitions from the SPD----------<br>avoirdupois (phr.) 'Would you like peas with that?'<br></div>distribute (v.) To denigrate a look-alike band.<br>
<div class="im">definite (phr.) 'It's hard of hearing, I think.'<br>modest (n.) The most mod.<br><br></div>
<div>
<div></div>
<div class="h5">On 5 Dec 2011, at 13:45, john doe wrote:<br><br>> Hello,<br>><br>> @ Mysurf: I asked almost the same questions about two weeks ago ("questions about RpcClient")<br>><br>> @ Steve: Nice to see that you are working on improving these classes. I actually had three major issues with RpcClient:<br>
> - the lack of interface which made mocking quite difficult for unit testing (I had to inherit from the class)<br>> - the fact that the routing key is a final attribute of the class (which makes me create multiple clients when using several routing keys)<br>
> - the lack of a "single request / multiple replies" scenario (with a expected number of replies and a timeout)<br>><br>> John<br><br></div></div></blockquote></div><br>