Not sure I understand this line in specification:

Clients SHOULD NOT close a connection by default, but MAY in case the content exceeds constraints set by the user.

=> https://geminiprotocol.net/docs/protocol-specification.gmi#closing-connections

Why should I keep connection open (on client-side), even the page has been loaded? Maybe just to prevent double handshake only?

Asking, because have some head pain with Rust implementation, where connection get dopped by last reference left the scope. So here simpler to open connection again, than hold and manage connection reference somewhere, e.g. in memory stack.

Just do I understand specification right to begin endless connection implementation?

Thanks

=> Posted in: s/Gemini | 👻 ps

2024-11-24 · 8 weeks ago

4 Comments ↓

=> 👻 ps [OP] · Nov 24 at 14:53:

So that's okay my connection get closed after last byte received. Now it looks correct. Maybe will return to this subject later, on media streaming implementation.

@HanzBrix hanks much for explain!

=> 🚀 stack · Nov 24 at 15:15:

How do you know what is the last byte?

=> 👻 ps [OP] · Nov 24 at 15:22:

@HanzBrix ah, exactly! it's just memory kidding me, wrote some gemini servers before, where closed connection after last byte sent. still thinking as server :)

=> 💀 requiem · Nov 25 at 19:56:

Keeping it open is also what enables TCP streaming over Gemini, there was some experimental chat software for it :)