From fd8da6db043c1571b3db3ba5fb8b46a5b36fae67 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 4 Oct 2019 10:34:20 -0500 Subject: [PATCH] Update noecho.md --- developer/connecting/noecho.md | 27 +-------------------------- 1 file changed, 1 insertion(+), 26 deletions(-) diff --git a/developer/connecting/noecho.md b/developer/connecting/noecho.md index 1ba5767..73a73c3 100644 --- a/developer/connecting/noecho.md +++ b/developer/connecting/noecho.md @@ -4,32 +4,7 @@ By default a NATS connection will echo messages if the connection also has inter The NoEcho option can be useful in BUS patterns where all applications subscribe and publish to the same subject. Usually a publish represents a state change that the application already knows about, so in the case where the application publishes an update it does not need to process the update itself. -
-digraph { - rankdir=LR; - subgraph cluster_1 { - shape=box; - style="rounded"; - label = "Connection #1"; - - publisher [shape=box, style="rounded", label="Publisher"]; - subscriber_1 [shape=box, style="rounded", label="Subscriber"]; - } - subgraph cluster_2 { - shape=box; - style="rounded"; - label = "Connection #2"; - - subscriber_2 [shape=box, style="rounded", label="Subscriber"]; - } - - subject [shape=circle, label="Subject"]; - - publisher -> subject [label="msg"]; - subject -> subscriber_1 [label="echo'd msg", style="dashed"]; - subject -> subscriber_2 [label="msg"]; -} -
+![noecho](/assets/images/noecho.svg) Keep in mind that each connection will have to turn off echo, and that it is per connection, not per application. Also, turning echo on and off can result in a major change to your applications communications protocol since messages will flow or stop flowing based on this setting and the subscribing code won't have any indication as to why.