taigrr/nats.docs
1
0
Fork 0
mirror of https://github.com/taigrr/nats.docs synced 2025-01-18 04:03:23 -08:00
Code Issues Projects Releases Wiki Activity

updates based on RI changes to README

Browse Source
This commit is contained in:
Ginger Collison
2021-02-05 14:35:01 -06:00
committed by GitHub
parent 6875a3fab9
commit 501ecd83dc
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
jetstream/administration/consumers.md
View File

@@ -184,11 +184,11 @@ Acknowledged message
You can prevent ACKs by supplying `--no-ack`.
To do this from code you'd send a `Request()` to `$JS.NEXT.ORDERS.DISPATCH`:
To do this from code you'd send a `Request()` to `$JS.API.CONSUMER.MSG.NEXT.ORDERS.DISPATCH`:
```
$ nats req '$JS.NEXT.ORDERS.DISPATCH' ''
Published [$JS.NEXT.ORDERS.DISPATCH] : ''
$ nats req '$JS.API.CONSUMER.MSG.NEXT.ORDERS.DISPATCH' ''
Published [$JS.API.CONSUMER.MSG.NEXT.ORDERS.DISPATCH] : ''
Received [ORDERS.processed] : 'order 3'
```
@@ -216,4 +216,4 @@ Listening on [monitor.ORDERS]
Note the subject here of the received message is reported as `ORDERS.processed` this helps you distinguish what you're seeing in a Stream covering a wildcard, or multiple subject, subject space.
This Consumer needs no ack, so any new message into the ORDERS system will show up here in real time.
This Consumer needs no ack, so any new message into the ORDERS system will show up here in real time.