💾 Archived View for rawtext.club › ~sloum › geminilist › 007694.gmi captured on 2024-03-21 at 15:40:03. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-08)
-=-=-=-=-=-=-
Luke Emmet luke at marmaladefoo.com
Mon Dec 13 21:38:04 GMT 2021
- - - - - - - - - - - - - - - - - - -
On 13-Dec-2021 20:55, Krixano wrote:
that portion of text no longer even being present in the latest version of the spec on gitlab: https://gitlab.com/gemini-specification/protocol/-/blob/master/specification.gmi
Thanks for the link to the updated protocol, I was just going on the version on the gemini home capsule as the official version.
Clearly whatever solderpunk puts in is what the spec is. And there is less said now in the current draft of the spec about the expected interleaving of client and server events. This leaves more room for servers to expect clients to process the data before it is completed.
Still it seems unclear to me how a client can now tell between a faulty or excessively slow server and one that is valid but is streaming content very slowly. In the previous draft the expectation was the client waits for content, which will conclude, then it is processed. Now clients don't get to have a general expectation that the content will conclude or not as it comes down the pipe.
Probably the best option is to try to guess whether the content might be a stream from the media type as spc suggests, although that seems like guesswork to me.
Anyway, clients and servers probably need to have a connection timeout to prevent tar pits.
regards
- Luke