You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,6 +376,7 @@ rpc_clients:
376
376
integer_store:
377
377
connection: default
378
378
unserializer: json_decode
379
+
direct_reply_to: false
379
380
rpc_servers:
380
381
random_int:
381
382
connection: default
@@ -476,6 +477,12 @@ public function indexAction($name)
476
477
477
478
Is very similar to the previous example, we just have an extra `addRequest` call. Also we provide meaningful request identifiers so later will be easier for us to find the reply we want in the __$replies__ array.
478
479
480
+
### Direct Reply-To clients ###
481
+
482
+
To enable [direct reply-to clients](https://www.rabbitmq.com/direct-reply-to.html) you just have to enable option __direct_reply_to__ on the __rpc_clients__ configuration for the client.
483
+
484
+
This option will use pseudo-queue __amq.rabbitmq.reply-to__ when doing RPC calls. On the RPC server there is no modification needed.
485
+
479
486
### Multiple Consumers ###
480
487
481
488
It's a good practice to have a lot of queues for logic separation. With a simple consumer you will have to create one worker (consumer) per queue and it can be hard to manage when dealing
0 commit comments