Client behavior when server doesn't close connection?



> On Jul 9, 2020, at 15:14, defdefred <defdefred at protonmail.com> wrote:
> 
> On Thursday 9 July 2020 14:52, Petite Abeille <petite.abeille at gmail.com> wrote:
>>> And what about binary content?
>> 
>> Use a different protocol.
> 
> Gemini can't send image?

Sure it can. But perhaps it shouldn't. Depends on how much reliability one is after.

See "File size" in "Best practices for Gemini implementations":
https://portal.mozz.us/gemini/gemini.circumlunar.space/docs/best-practices.gmi


Gemini servers do not inform clients of the size of files they are 
serving, which can make it difficult to detect if a connection is closed 
prematurely due to a server fault.  This risk of this happening increases with file size.

Gemini also has no support for compression of large files, or support for 
checksums to enable detection of file corruption, the risk of which also 
increases with file size.

For all of these reasons, Gemini is not well suited to the transfer of 
"very large" files.  Exactly what counts as "very large" depends to some 
extent on the speed and reliability of the internet connections involved, 
and the patience of the users.  As a rule of thumb, files larger than 
100MiB might be thought of as best served some other way.

Of course, because Gemini supports linking to other online content via any 
protocol with a URL scheme, it's still possible to link from a Gemini 
document to a large file served via HTTPS, BitTorrent, IPFS or whatever 
else tickles your fancy.


Replace "very large file" with binary and you get the gist of it.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20200709/421a
498b/attachment.htm>

---

Previous in thread (4 of 16): 🗣️ defdefred (defdefred (a) protonmail.com)

Next in thread (6 of 16): 🗣️ juhani (juhani (a) envs.net)

View entire thread.