Ali Fardan <raiz at stellarbound.space> wrote: > > Scenario 3: download a big file > [...] Implementing this would be tricky on the server side, this would add > unnecessary complexity, Yes, the server would need to be able to accept and respond to other connections while the file is transmitted. It also needs either be able to run CGI scripts or have custom code for that endpoint. what I would suggest instead if you really insist on using Gemini for large > file transfers is specifying file size > in the link label like so: > > => gemini://example.tld/large_file.bin Download (140 MB) > > and then have the client show how much of the file is downloaded, now > that you know the file size, and know how much is downloaded, you don't > need a progress indicator to be implemented within the protocol. Of > course this is on the client to implement, but wouldn't be tricky at > all. > Foster an environment where capsule authors are good enough internet citizens to always provide the file size on the page? Sure, that wouldn't be tricky at all. Corrected: Scenario 3.1: download a big file and the capsule author neglected to provide a file size > Scenario 4: the TLS session terminated cleanly but we don't have full > > confidence the download succeed > > > > Verify the file using the information we have (from scenario 3) or > > present the user with the option to fetch a hash from the > > standardized endpoint. > > This does not have to be embedded in the protocol, just do this: > > SHA1: ad7ff785f989c9ff9cec92bd3d0bab035a54e997 > SHA256: d2af944fe8b3af5cf5a9d8c3226d06ac6369d036fc591363dedc85344bc4daa7 > => gemini://example.tld/large_file.bin Download (140 MB) > > now the user can verify their downloaded file, this is done all the > time even in HTTP land. > I would personally prefer the way we did it with FTP and provide a large_file.bin.md5sum or now large_file.bin.sha1sum, but I would use another protocol for large files. -- Katarina > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201105/b785 3464/attachment.htm>
---
Previous in thread (5 of 9): 🗣️ acdw (acdw (a) acdw.net)
Next in thread (7 of 9): 🗣️ Ali Fardan (raiz (a) stellarbound.space)