General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: flent-users@flent.org
Cc: bloat@lists.bufferbloat.net
Subject: [Bloat] What is your favourite Flent feature?
Date: Tue, 25 Apr 2017 13:49:11 +0200	[thread overview]
Message-ID: <87zif4btc8.fsf@alrua-kau> (raw)

Hey everyone

I finally got around to a much-needed freshening of the front page on
https://flent.org/ - so it now contains a feature list and a screen shot
as the first content. I've also recently written a blog post[1]
highlighting some of Flent's features, and Flent was recently featured
on Google's Open Source Peer Bonus programme[2].

Since I am planning on writing an expanded version of the short paper[3]
describing Flent, I thought I would solicit some feedback on what to
focus on. I envision something that is structured to showcase one or
more of Flent's features by going through an example experiment.

So, here's my question: What feature(s) would you most like to see in
such an article? Whether it's because it is something that you like and
use, and so feel is important to showcase, or because it's something
that you would like to see explained better; any input is welcome. Feel
free to use the feature list on flent.org or in the blog post as
inspiration; or come up with your own :)

Many thanks in advance,

-Toke

[1] https://blog.tohojo.dk/2017/04/the-story-of-flent-the-flexible-network-tester.html
[2] https://opensource.googleblog.com/2017/03/the-latest-round-of-google-open-source.html
[3] https://flent.org/flent-the-flexible-network-tester.pdf

             reply	other threads:[~2017-04-25 11:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 11:49 Toke Høiland-Jørgensen [this message]
     [not found] <mailman.1.1493136001.28854.bloat@lists.bufferbloat.net>
2017-04-26  1:35 ` Rich Brown
2017-04-27 11:16   ` 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=87zif4btc8.fsf@alrua-kau \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=flent-users@flent.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