General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Isaac Konikoff <konikofi@candelatech.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] The Great Renaming (of netperf-wrapper): Final contenders
Date: Tue, 14 Apr 2015 10:30:47 -0700	[thread overview]
Message-ID: <552D4EC7.2030101@candelatech.com> (raw)
In-Reply-To: <87pp782wbt.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1897 bytes --]

Exnett is great, it brings the word examine to mind, but you might have 
to forever explain the second t.

NetBasher is also a close second, but makes me think the tool is 
destructive in some way.

I also like netpert or nexpert, but maybe they're too close to netexpert 
<http://en.wikipedia.org/wiki/NetExpert> or netperf itself.

netpert - network performance test

nexpert - network extensible performance test

Good luck with your decision!

p.s. I keep getting the following stuck in my head as well, netpow and 
netpewpew (laser cats reference), but they might be difficult to say 
with a straight face :)

Isaac





On 04/13/2015 02:48 AM, Toke Høiland-Jørgensen wrote:
> Hi everyone
>
> The Great Renaming (of netperf-wrapper) has now entered its final phase
> (i.e., I have to make a decision now). There's a couple of contenders
> for a new name, see below. I'd like some feedback on which you prefer. A
> simple "This one!" is fine, but reasoning about why is also appreciated,
> of course :)
>
> So, without further ado, the contenders are:
>
> - "ENT: The Extensible Network Tester".
>    Possible name clash:https://packages.debian.org/sid/ent
>
> - "Exnett: The EXtensible NETwork Tester"
>     Avoids the name clash; the second t is important for this.
>
> - "Flent: The Flexible Network Tester"
>    'Flent' is also the sound a bufferbloated network makes when subjected
>    to testing :)
>
> - "NetBasher"
>
> For the first three, the abbreviation would probably be the everyday
> name, name of the executable, etc, with the expansion added in
> descriptions where appropriate.
>
>
> Please comment by Thursday, as I have a deadline for something that
> needs to include the name then...
>
> Thanks in advance! :)
>
> -Toke
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>


[-- Attachment #2: Type: text/html, Size: 2614 bytes --]

  parent reply	other threads:[~2015-04-14 17:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13  9:48 Toke Høiland-Jørgensen
2015-04-13 14:58 ` Bill Ver Steeg (versteb)
2015-04-13 15:36 ` Dave Taht
2015-04-14 17:30 ` Isaac Konikoff [this message]
2015-04-18 12:46 ` Toke Høiland-Jørgensen

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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=552D4EC7.2030101@candelatech.com \
    --to=konikofi@candelatech.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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