Revisiting Streams (Briefly?)
I feel that this should be revisited to make sure that this is an intended consideration of the protocol, and that the spec agrees with this intended consideration.
Previously, I believe Solderpunk was all for allowing "Streams" as long as it didn't result in a new status code. This would simply require being able to read the data as it is streamed in rather than waiting for all the data to be received at once. The other consideration was the handling of timeouts when clients did not receive data during a period of time, and if this is necessary when there's now a requirement for close_notify which will tell the client the request is complete. It would also seem that the current version of the spec on GitLab does allow for "streams" (aka. Handling data as it is streamed in).
However, opinions can always change, which is why I think this should be (hopefully briefly) revisited.
Here's a list of links talking about the idea of streaming within Gemini:
On Inputs and Client Certificates: gopher://zaibatsu.circumlunar.space:70/0/~solderpunk/gemini/inputs-and-client-certs.txt
On Streaming (Tomasino): gemini://rawtext.club/~sloum/geminilist/001696.gmi
On Applications and Streaming (Solderpunk): gemini://gemini.circumlunar.space/users/solderpunk/gemlog/a-vision-for-gemini-applications.gmi
Mozz's Response to Solderpunk on Streaming: gemini://mozz.us/journal/2020-06-21.gmi
Links via Gemini:
On Inputs and Client Certificates: gemini://zaibatsu.circumlunar.space/~solderpunk/gemini/inputs-and-client-certs.txt
On Streaming (Tomasino): [Only Available Via Gopher, afaik]
On Applications and Streaming (Solderpunk): gemini://gemini.circumlunar.space/users/solderpunk/gemlog/a-vision-for-gemini-applications.gmi
Mozz's Response to Solderpunk on Streaming: [Only Available Via Gopher, afaik]
I'd also like to provide an additional link that shows a real-world case of streams being used with gemtext: gemini://gemini.thegonz.net/sggs/