News for hackers. Stuff that matters.
Re:Closing web browser windows doesn't close connections by woodruffw on Tuesday March 23, 2021 @10:21PM (#26562836)
I'll admit that I haven't looked closely at Gemini, but I don't understand how it solves this qua protocol: keepalives and socket reuse are an extension of HTTP that every major client agreed upon as a performance win, and Gemini has response headers[1] that clients could easily use to advertise similar functionality.

Same goes for any number of terrible parts of the modern web: the fact that Gemini doesn't have them now is a function of its niche status and community, not some fundamental restriction. That's how HTTP 1.0 started as well.

[1]: https://gemini.circumlunar.space/docs/specification.html

Re:Closing web browser windows doesn't close connections by Arnavion on Tuesday March 23, 2021 @11:32PM (#26563275)
There's no content-length header in the response. The server has to close the connection to signal the end of the response body.
Re:Closing web browser windows doesn't close connections by woodruffw on Tuesday March 23, 2021 @11:51PM (#26563406)
> There's no content-length header in the response.

I'm not sure I understand -- what's stopping me from adding one? One of Gemini's design goals seems to be client diversity and allowing clients to interpret responses on their own terms.

Edit: To be even more explicit about it: the Gemini specification doesn't include any language that says that clients and servers MUST not use the "meta" field or their response bodies to negotiate additional functionality. The observation that nobody in the Gemini ecosystem currently does is tantamount to the observation that nobody has bothered to yet, just like with HTTP 1.0.

Re:Closing web browser windows doesn't close connections by Arnavion on Wednesday March 24, 2021 @12:58AM (#26563754)
>One of Gemini's design goals seems to be client diversity and allowing clients to interpret responses on their own terms.

No, the design goal is the exact opposite of that. The protocol is intentionally designed to be non-extensible so that other features that go against its spirit are not added.

You can of course add a content-length header to your server and write your own client that parses it, but you wouldn't be writing a Gemini server and client any more.

https://gemini.circumlunar.space/docs/faq.gmi goes in great length about this in section 2, and even specifically about (the lack of) content-length in section 2.12