From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Announcing Flent (formerly netperf-wrapper) v0.10.0
Date: Sun, 24 May 2015 19:55:09 +0200 [thread overview]
Message-ID: <87a8wtg8si.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw79bdW6B44j-ZosF0T6C6M051MuhAQeicNKWUCvz9VCUA@mail.gmail.com> (Dave Taht's message of "Sun, 24 May 2015 10:34:20 -0700")
Dave Taht <dave.taht@gmail.com> writes:
> This contained the never-merged (some licencing issues) web based
> parser for the data.
>
> https://github.com/bipulkkuri/netperf-wrapper
The main reason (apart from licensing issues) that it was never merged
was that I don't want to maintain two plotting implementations within
Flent itself. So the possible scenarios for a web-based viewer are, as I
see it, roughly:
1. Leverage the existing matplotlib plotting implementation to produce
javascript plots. This is issue #27
(https://github.com/tohojo/flent/issues/27) and depends on how well
the mpl-to-d3 library works in practice.
2. Replace the whole plotting implementation with a javascript-based
one, and serve that from within Flent itself.
3. Have an entirely separate web viewer implementation.
Which scenario that works best will probably to a large extent depend on
the actual use case this mystical beast is supposed to support. Which I
don't believe has been articulated properly...
-Toke
next prev parent reply other threads:[~2015-05-24 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-24 13:48 Toke Høiland-Jørgensen
2015-05-24 16:22 ` Dave Taht
[not found] ` <CAA93jw7Cfv8rQxTP4gcZFoziHSvt8fw6zxyeUBdS0Ukn_9VYUA@mail.gmail.com>
2015-05-24 17:14 ` Dave Taht
2015-05-24 17:34 ` Dave Taht
2015-05-24 17:55 ` Toke Høiland-Jørgensen [this message]
2015-05-24 18:05 ` Dave Taht
2015-05-24 18:16 ` Toke Høiland-Jørgensen
2015-05-24 18:34 ` Dave Taht
2015-05-29 6:09 ` Sebastian Moeller
2015-05-24 18:23 ` Dave Taht
2015-05-25 23:17 ` David Lang
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=87a8wtg8si.fsf@toke.dk \
--to=toke@toke.dk \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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