From: Dave Taht <dave.taht@gmail.com>
To: dews@lists.bufferbloat.net
Subject: [Dews] some hacking on multicast and torrent
Date: Mon, 4 Jun 2012 08:48:43 -0400 [thread overview]
Message-ID: <CAA93jw6mn1_wVtT7HSORbWESZMXNOsfJafsRC8pXJ6cCBzTEJg@mail.gmail.com> (raw)
I spent part of last week adding sensor, and gps messages to the babel
routing protocol,
as well as a few ccn-like ideas for short messages and things like magnet urls.
I'm not saying this is a 'design', I just wanted to figure out how
fast and how much
data could be easily propagated across a local lan, wireless, and
(say) a comcast
neighborhood segment, and it happened that I knew the babel codebase
and it has a working link local multicast implementation... more news on that
as it happens.
I also noticed this:
http://arstechnica.com/tech-policy/2011/04/japans-earthquake-didnt-even-slow-bittorrent-use/
--
Dave Täht
SKYPE: davetaht
http://ronsravings.blogspot.com/
reply other threads:[~2012-06-04 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAA93jw6mn1_wVtT7HSORbWESZMXNOsfJafsRC8pXJ6cCBzTEJg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=dews@lists.bufferbloat.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