<br><div class="gmail_quote">On Thu, Mar 11, 2010 at 9:03 PM, Nathaniel Haggard <span dir="ltr"><<a href="mailto:natester@gmail.com">natester@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Machine D sends a message to exchange E1 with routing key send_to_A to<br>
execute a remote procedure call on A. A replies back using another<br>
exchange E2 with routing key results_of_A, but A could easily use the<br>
key results_of_B. Does rabbitmq have a way of making A only use the<br>
key results_of_A?<br>
<br>
Only D can write to E1. A, B, C can write to E2. I suppose A, B, C<br>
are all different users in the system although that seems overkill.<br>
<br>
Is there a better way to make sure the results from an RPC to A are<br>
really from A and not from B?<br>
<br>
I think it would not scale well (in the thousands) if A, B, C each had<br>
permissions to write to one queue exchanges E2, E3, and E4, but maybe<br>
that's wrong too.<br>
<br>
-Nate<br><br></blockquote><div><br>I use the correlation_id header field to ensure I get the correct result for a message back. But maybe I'm misunderstanding your question.<br><br>I think the Erlang Client has a test example that implements RPC this way.<br>
<br>Robby<br> <br></div></div>