Skip to content

Commit 124679b

Browse files
committed
[docs] concepts. add note about difference between transport queue name and client
1 parent 5dcf4bd commit 124679b

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

Diff for: docs/concepts.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -63,8 +63,7 @@ It provides extension points which could be ad-hoc into processing flow. You can
6363
Enqueue Client is designed for as simple as possible developer experience.
6464
It provides high-level, very opinionated API.
6565
It manage all transport differences internally and even emulate missing features (like publish-subscribe).
66-
67-
_*Note:* The client topic is NOT the same thing as transport one._
66+
Please note: Client has own logic for naming transport destinations. Expect a different transport queue\topic name from the Client topic, command name. The prefix behavior could be disabled.
6867

6968
- *Topic:* Send a message to the topic when you want to notify several subscribers that something has happened. There is no way to get subscriber results. Uses the router internally to deliver messages.
7069
- *Command:* guaranty that there is exactly one command processor\subscriber. Optionally, you can get a result. If there is not a command subscriber an exception is thrown.

0 commit comments

Comments
 (0)