💾 Archived View for rawtext.club › ~sloum › geminilist › 007630.gmi captured on 2021-11-30 at 19:37:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Scot gmi1 at scotdoyle.com
Tue Nov 23 21:06:32 GMT 2021
- - - - - - - - - - - - - - - - - - -
On Tue, 23 Nov 2021 08:57:43 +0100Omar Polo <op at omarpolo.com> wrote:
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 clearest
way to do so is just streamingly parsing the output as soon as it
arrives. If you don't get a close_notify at the end you can just as
well delete the page and render an error if you want.
(also, you won't be able to handle streaming pages if you wait for the
server to close the connection)
Agreed. A nice side effect (imo) of specifying that clients arepermitted to start handling requests right away is that thestreaming use case is included.