💾 Archived View for bbs.geminispace.org › u › HanzBrix › 22147 captured on 2024-12-17 at 15:49:35. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Re: "Not sure I understand this line in specification: Clients..."
@ps No problem. 😁
It's not after last byte received though, as that would not follow the spec. It is once you get a close signal from the server on the TLS connection.
This behaviour is also what allows the impromptu streaming, but it also allows Gemini clients to load really fast, as they can begin processing the buffer, before they have received everything.
Nov 24 · 3 weeks ago
How do you know what is the last byte?
@HanzBrix ah, exactly! it's just memory kidding me, wrote some gemini servers before, where closed connection after last byte sent. still thinking as server :)
Keeping it open is also what enables TCP streaming over Gemini, there was some experimental chat software for it :)
Not sure I understand this line in specification: Clients SHOULD NOT close a connection by default, but MAY in case the content exceeds constraints set by the user. [https link] Why should I keep connection open (on client-side), even the page has been loaded? Maybe just to prevent double handshake only? Asking, because have some head pain with Rust implementation, where connection get dopped by last reference left the scope. So here simpler to open connection again, than hold and manage...