From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8813c14c2411f3c38f30016f85394078@terzarima.net>
To: 9fans@9fans.net
From: Charles Forsyth <forsyth@terzarima.net>
Date: Mon, 21 Apr 2008 22:24:35 +0100
In-Reply-To: <20080421210627.D6D915B66@mail.bitblocks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] telnet vs. godaddy whois
Topicbox-Message-UUID: 96e458d2-ead3-11e9-9d60-3106f5b1d025

>      must not buffer data indefinitely, and (2) MUST set the
>      PSH bit in the last buffered segment (i.e., when there
>      is no more queued data to be sent).
>
> The implication is that the "preceding segment" to a pkt with
> no data *will have* PSH set.

so does the implementation do that?
can you prove it in all cases?
what will break if we just change it without knowing?
after all, it has been 15 years to come across a botched receiver's implementation
of PSH (ie, godaddy's) which is the only reason to change it.
that's what i was pointing out. i could do the work myself, i suppose, but i haven't got the incentive.

>here you have to be compatible with existing
>implementations as far as possible (in order to maximize
>interoperability).

i suspect arguments like that caused the current situation with HTML, CSS and Javascript.
computing is needlessly regressing.