From: Juliusz Chroboczek <jch@irif.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: galene@lists.galene.org
Subject: [Galene] Re: Peer-to-peer file transfer in Galene
Date: Sun, 30 Jan 2022 19:19:58 +0100 [thread overview]
Message-ID: <87tudl84s1.wl-jch@irif.fr> (raw)
In-Reply-To: <CAA93jw7yOJYFCNph_ik2_HpE5qZTJ6WAtLz7fGtsa9_nFyi4+w@mail.gmail.com>
> Well, the still half formed torrent-like thought was that it would be
> torrent-like so that different chunks of the file went to different
> locations and were meshed from there.
The simple solution is to upload the file to the server and make it
available to clients over HTTP(S). This also avoids disclosing IP
addresses.
The only con is that it requires storage on the server, which might or
might not be available.
-- Juliusz
next prev parent reply other threads:[~2022-01-30 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 16:40 [Galene] " Juliusz Chroboczek
2022-01-30 16:44 ` [Galene] " Juliusz Chroboczek
2022-01-30 16:45 ` Dave Taht
2022-01-30 17:22 ` Juliusz Chroboczek
2022-01-30 17:34 ` Dave Taht
2022-01-30 18:00 ` Juliusz Chroboczek
2022-01-30 18:12 ` Dave Taht
2022-01-30 18:19 ` Juliusz Chroboczek [this message]
2022-01-30 18:23 ` Dave Taht
2022-01-30 18:34 ` Juliusz Chroboczek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tudl84s1.wl-jch@irif.fr \
--to=jch@irif.fr \
--cc=dave.taht@gmail.com \
--cc=galene@lists.galene.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox