From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: * X-Spam-Status: No, score=1.3 required=5.0 tests=RDNS_NONE autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 19317 invoked from network); 31 Aug 2021 09:07:26 -0000 Received: from unknown (HELO 4ess.inri.net) (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 31 Aug 2021 09:07:26 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Tue Aug 31 03:56:03 -0400 2021 Message-ID: <41DB60AECD3C313EFF46C7CFB680A537@felloff.net> Date: Tue, 31 Aug 2021 09:55:51 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: <6C770927-6695-4440-B1D2-4C42B9EADE43@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: full-stack storage lifecycle realtime-java frontend Subject: Re: [9front] rconnect via aan reliability patch Reply-To: 9front@9front.org Precedence: bulk how does this work? how is adding another roundtrip fixing a hung up tcp connection? the patch is probably fine, but i do not understand what it is fixing here... -- cinap