Cache duration and response body size proposals

[Robert "khuxkm" Miles]

November 10, 2020 10:29 AM, "Philip Linde" <linde.philip at gmail.com> wrote:

> On Tue, 10 Nov 2020 15:11:54 +0000
> "Robert \"khuxkm\" Miles" <khuxkm at tilde.team> wrote:
> 
>> I mean, yes, that's the point of close_notify, but what if the connection dies *after* the data is
>> sent but *before* the close_notify can be sent? Then it turns into an unsolvable two-generals
>> problem.
> 
> Then you don't know that you received the complete data. You can
> safely apply the same strategy as you would if you *did* know that you
> didn't receive the complete data. It's only a problem if you make it
> one.
> 
> --
> Philip

But then this goes back to the whole discussion we had about caching: sure, the overhead of a TLS connection is low, but it's not zero. If I know for a fact that the response I got has as many bytes as I was told I had, then even in the absence of a close_notify, I know for a fact I have the whole response and can be sure in that. (If I get a close_notify while not having as many bytes, I can just assume the server either lied or something else broke, and I can ask my user what to do.)

Just my two cents,
Robert "khuxkm" Miles