From eee190b33dcd0c772fd4b46871dba7eeccb78b5b Mon Sep 17 00:00:00 2001 From: Dimitri Staessens Date: Mon, 28 Feb 2022 19:55:08 +0100 Subject: blog: Small fix in flow liveness monitoring --- content/en/blog/20220228-flow-liveness-monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content') 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 -- cgit v1.2.3