From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] btfs, a BitTorrent client (attempt)
Date: Thu, 16 Jul 2009 14:44:05 -0400 [thread overview]
Message-ID: <bf7be003a666abaf04362555e997dc73@quanstro.net> (raw)
In-Reply-To: <8ace18cfdc26bf96b994af920c6e77e9@smgl.fr.eu.org>
> So as a first approach I was thinking of having simply one thread for
> each connection with a peer. And maybe one group of threads (in one
> process) would be responsible for getting the pieces, while another
> one (in another process) would be responsbile for sending the pieces
> we have. How does that sound?
why can't they communicate through the filesystem?
i would imagine you could avoid building a lot of
fancy infastructure if you did it that way.
- erik
next prev parent reply other threads:[~2009-07-16 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 18:35 Mathieu L.
2009-07-16 18:44 ` erik quanstrom [this message]
2009-07-16 18:46 ` Mathieu L.
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=bf7be003a666abaf04362555e997dc73@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).