From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Caleb Shay <caleb@webninja.com>
Cc: Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] torrent support in portage
Date: 14 Apr 2003 20:42:34 -0400 [thread overview]
Message-ID: <m3vfxgfv5x.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <1050351263.19545.20.camel@chinstrap.penguins.homeunix.net>
Note that bittorrent does not work very well for dialup users. The
overhead ends up being twice as large or more than the payload. It
also ends up blocking most other traffic.
It generally helps for those with more bandwidth, of course, but
something that does not open a couple of hundred sockets works
better over straws.
It will work well as a supplement to the staus quo,
but not so well as a replacement.
-JimC
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-15 0:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 20:14 [gentoo-dev] torrent support in portage Caleb Shay
2003-04-15 0:42 ` James H. Cloos Jr. [this message]
2003-04-15 0:49 ` Caleb Shay
2003-04-15 5:24 ` James H. Cloos Jr.
2003-04-15 8:15 ` Brian Friday
2003-04-15 12:24 ` James H. Cloos Jr.
2003-04-15 8:09 ` Ragnar Hojland Espinosa
2003-04-15 1:38 ` Robin H.Johnson
2003-04-15 13:55 ` Caleb Shay
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=m3vfxgfv5x.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=caleb@webninja.com \
--cc=gentoo-dev@gentoo.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