From: Mark H Weaver <mhw@netris.org>
To: Pierre-Antoine Rault <par@rigelk.eu>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: [GSoC] GNUnet binary distribution system
Date: Mon, 10 Mar 2014 23:35:11 -0400 [thread overview]
Message-ID: <87a9cxif0w.fsf@yeeloong.lan> (raw)
In-Reply-To: <531E4894.7080103@rigelk.eu> (Pierre-Antoine Rault's message of "Tue, 11 Mar 2014 00:19:48 +0100")
Pierre-Antoine Rault <par@rigelk.eu> writes:
> On 10/03/2014 22:09, Ludovic Courtès wrote:
>>
>> The initial discussion [0] left open the question of where
>> binaries themselves should be stored. A possibility would be to
>> use GNUnet’s DHT simply as a discovery mechanism, and then to
>> establish a connection directly to the user’s machine, which would
>> run, say, an HTTP server.
>
> That's what I had in mind. Now, considered the post [2] by Christian
> Grothoff, we might consider using either an HTTP server for
> performance or GNUnet's MESH for anonymity (and security). We should
> balance needs and ease of implementation.
>
> [2] http://lists.gnu.org/archive/html/guix-devel/2014-03/msg00113.html
FWIW, I think it might be worthwhile to support BitTorrent magnet links
as well, as a middle ground between these two extremes. Most users will
not be able to host binaries via HTTP; even if they have a server, the
bandwidth requirements are hard to predict and likely to be too high.
Mark
next prev parent reply other threads:[~2014-03-11 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 18:41 [GSoC] GNUnet binary distribution system Pierre-Antoine Rault
2014-03-10 21:09 ` Ludovic Courtès
2014-03-10 22:03 ` Christian Grothoff
2014-03-10 22:26 ` Ludovic Courtès
2014-03-10 23:19 ` Pierre-Antoine Rault
2014-03-11 3:35 ` Mark H Weaver [this message]
2014-03-11 6:59 ` Pierre-Antoine Rault
2014-03-11 18:29 ` Mark H Weaver
2014-03-11 8:42 ` Christian Grothoff
2014-03-11 13:06 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9cxif0w.fsf@yeeloong.lan \
--to=mhw@netris.org \
--cc=gnunet-developers@gnu.org \
--cc=guix-devel@gnu.org \
--cc=par@rigelk.eu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.