💾 Archived View for rawtext.club › ~sloum › geminilist › 007627.gmi captured on 2023-11-14 at 08:27:40. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Omar Polo op at omarpolo.com
Tue Nov 23 07:57:43 GMT 2021
- - - - - - - - - - - - - - - - - - -
Scot <gmi1 at scotdoyle.com> writes:
Hi all,
The transaction sequence in section 1.1 seems to read chronologically,
which would mean clients are not permitted to handle any of the
response until the server closes the connection.
I don't know how every gemini client handle this, but IMHO the clearestway to do so is just streamingly parsing the output as soon as itarrives. If you don't get a close_notify at the end you can just aswell delete the page and render an error if you want.
(also, you won't be able to handle streaming pages if you wait for theserver to close the connection)
Would it make sense to clarify this in the spec, maybe by changing
the last line of section 1.1 or by adding a note to section 3.4?
No. The transaction sequence shows the steps, it's not written anywherethat some of those steps can't happen in parallel.
Scot