From: David Lang <david@lang.hm>
To: Valdis.Kletnieks@vt.edu
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Recording RF management info _and_ associated traffic?
Date: Sun, 25 Jan 2015 20:39:23 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1501252032470.19609@nftneq.ynat.uz> (raw)
In-Reply-To: <11071.1422246330@turing-police.cc.vt.edu>
On Sun, 25 Jan 2015, Valdis.Kletnieks@vt.edu wrote:
>> The Computer Scientist will cringe at the 'hacks' that this introduces, but
>> there is far more progress made when new capabilities can be added in a way
>> that's transparent to other layers of the stack then when it requires major
>> changes to how things work.
>
> Otherwise known as the "Just throw an F5 in front of the whole mess" school
> of network design... :)
Much as you may hate the abuse of standards and protocols that F5 and other load
balancers use to trick both clients and servers into operating without knowing
that there are multiple machines serving a website, they do make things a lot
more better than if you tried make a website reliable and scale without them.
"theoretically better" is trumped by "it works" any day. For something that's
theoretically better to win it needs to be implemented and be better in practice
as well.
David Lang
next prev parent reply other threads:[~2015-01-26 4:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 2:20 Richard Smith
2015-01-20 16:59 ` Rich Brown
2015-01-21 23:40 ` Richard Smith
2015-01-21 23:58 ` David Lang
2015-01-22 9:04 ` Richard Smith
2015-01-22 9:18 ` David Lang
2015-01-22 18:19 ` Richard Smith
2015-01-22 22:09 ` David Lang
2015-01-22 22:55 ` Roman Toledo Casabona
2015-01-24 14:59 ` dpreed
2015-01-24 15:30 ` Kelvin Edmison
2015-01-25 4:35 ` David Lang
2015-01-25 5:02 ` Dave Taht
2015-01-25 5:04 ` Dave Taht
2015-01-25 6:44 ` David Lang
2015-01-25 7:06 ` David Lang
[not found] ` <CAA93jw64KjW-JjLxB3i_ZK348NCyJYSQACFO34MaUsBBWyZ+pA@mail.gmail.com>
2015-01-25 7:59 ` Dave Taht
2015-01-25 9:39 ` David Lang
2015-01-25 15:03 ` Chuck Anderson
2015-01-25 20:17 ` dpreed
2015-01-25 23:21 ` Aaron Wood
2015-01-25 23:57 ` David Lang
2015-01-26 1:51 ` dpreed
2015-01-26 2:09 ` David Lang
2015-01-26 4:33 ` Valdis.Kletnieks
2015-01-26 4:44 ` David Lang
2015-01-27 0:14 ` dpreed
2015-01-27 0:23 ` David Lang
2015-01-26 2:19 ` Dave Taht
2015-01-26 2:43 ` David Lang
2015-01-26 2:58 ` Dave Taht
2015-01-26 3:17 ` dpreed
2015-01-26 3:32 ` David Lang
2015-01-26 3:45 ` Dave Taht
2015-01-27 0:12 ` dpreed
2015-01-27 0:31 ` David Lang
2015-01-27 0:36 ` Dave Taht
2015-01-26 3:19 ` David Lang
2015-01-26 4:25 ` Valdis.Kletnieks
2015-01-26 4:39 ` David Lang [this message]
2015-01-26 16:42 ` Valdis.Kletnieks
2015-01-25 8:07 ` Outback Dingo
2015-01-30 16:14 ` Richard Smith
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.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1501252032470.19609@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=Valdis.Kletnieks@vt.edu \
--cc=cerowrt-devel@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