Scot <gmi1@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) > 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 anywhere that some of those steps can't happen in parallel. > Scot
---
Previous in thread (2 of 8): 🗣️ lincoln auster (lincolnauster (a) gmail.com)
Next in thread (4 of 8): 🗣️ Jonathan Lamothe (jlamothe (a) posteo.net)