File size issues

[solderpunk]

> Does TLS not have a native way to handle this? I did a quick search and found
> that either the client/server may send a close_notify message before
> terminating a TLS connection.
> 
>     https://tools.ietf.org/html/rfc5246#section-7.2.1

Ah, this is a great detail to have noticed!  I'll need to look into how
hard it typically is for clients to check that they've received this.
If it's straightforward, it's probably a good idea to amend the spec to
say that servers MUST send this close_notify message.  That would then
act as an analogue of Gopher's lone dot.

> I agree with this sentiment. Knowing the file size would be nice to have, but I
> haven't seen any use cases that are compelling enough to justify increasing the
> complexity to the protocol for. Even in HTTP land, Content-Length is an optional
> response header and there are several scenarios where it doesn't make sense to
> include it at all.

Yeah, I think we can leave this for now.  It was a hypothetical concern
that somebody had.  Not necessarily a bad one, but until it's observed
actually creating significant trouble for actual users on actual clients
I think we can just table this issue.  If it does come up as a practical
concern, we can resume discussion of some of the ideas here.

-Solderpunk