aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDimitri Staessens <[email protected]>2022-02-28 19:55:08 +0100
committerDimitri Staessens <[email protected]>2022-02-28 19:55:08 +0100
commiteee190b33dcd0c772fd4b46871dba7eeccb78b5b (patch)
treeb6fa81aedc7be43e7e36b057581c9632f478e40f
parentb116e6470da9177c178ad63a7d5e3a705448fba3 (diff)
downloadwebsite-eee190b33dcd0c772fd4b46871dba7eeccb78b5b.tar.gz
website-eee190b33dcd0c772fd4b46871dba7eeccb78b5b.zip
blog: Small fix in flow liveness monitoring
-rw-r--r--content/en/blog/20220228-flow-liveness-monitoring.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/content/en/blog/20220228-flow-liveness-monitoring.md b/content/en/blog/20220228-flow-liveness-monitoring.md
index ba9190f..e94d5a0 100644
--- a/content/en/blog/20220228-flow-liveness-monitoring.md
+++ b/content/en/blog/20220228-flow-liveness-monitoring.md
@@ -82,7 +82,7 @@ Failed to read packet: -1006.
How does it work?
In the
-[first post on this topic]([post](/blog/2021/12/29/behaviour-of-ouroboros-flows-vs-udp-sockets-and-tcp-connections/sockets/),
+[first post on this topic](/blog/2021/12/29/behaviour-of-ouroboros-flows-vs-udp-sockets-and-tcp-connections/sockets/),
I explained my reasoning how Ouroboros should deal with half-closed
flows (flow deallocation from one side should eventually result in a
terminated flow at the other side). The implementation should work