From b28a39477d7cbd38feda2c09c7dafdffe89c45b4 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Tue, 11 Jun 2019 10:26:55 -0500 Subject: [PATCH] updating go nats-pub example path from nats-site PR #440 --- developer/tutorials/queues.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/developer/tutorials/queues.md b/developer/tutorials/queues.md index e7ccc03..670720e 100644 --- a/developer/tutorials/queues.md +++ b/developer/tutorials/queues.md @@ -24,7 +24,7 @@ git clone https://github.com/nats-io/ruby-nats.git ```sh cd $GOPATH/src/github.com/nats-io/nats.go/examples -go run nats-qsub.go foo my-queue +go run nats-qsub/main.go foo my-queue ``` ### 4. Install and run the Node client subscriber with queue group name @@ -46,14 +46,14 @@ nats-queue foo my-queue & ```sh cd $GOPATH/src/github.com/nats-io/nats.go/examples -go run nats-sub.go foo +go run nats-sub/main.go foo ``` ### 7. Publish a NATS message using the Go client ```sh cd $GOPATH/src/github.com/nats-io/nats.go/examples -go run nats-pub.go foo "Hello NATS!" +go run nats-pub/main.go foo "Hello NATS!" ``` ### 8. Verify message publication and receipt @@ -65,7 +65,7 @@ You should see that only one of the my-queue group subscribers receives the mess ### 9. Publish another message ```sh -go run nats-pub.go foo "Hello NATS Again!" +go run nats-pub/main.go foo "Hello NATS Again!" ``` You should see that a different queue group subscriber receives the message this time, chosen at random among the 3 queue group members.