From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 08DE921F25D for ; Sun, 24 May 2015 10:55:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1432490110; bh=TKpZXHnI2dY/ejXa1DRB+6i0evZ0KrixsKxs8gZOzSI=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=cByjEDsq6iN4PuhS64kI31IiKUW7H6nM0/gfP2p9XNcqx3Qw3/Q6ljI/RqRLbF1Tx p5wd9IgR0/1swZRQ2gkvh3ZXYpXoQw7CeBEUlwIffoXJtA5VWvF9UjgypQmbckWHF7 iJHgKYb9nZQhpZIMHWiTZh8GpZgWRUhE63nRROnY= Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id 92D7A38BBBC; Sun, 24 May 2015 19:55:09 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Dave Taht References: <877frygk7e.fsf@toke.dk> Date: Sun, 24 May 2015 19:55:09 +0200 In-Reply-To: (Dave Taht's message of "Sun, 24 May 2015 10:34:20 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87a8wtg8si.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Cc: bloat Subject: Re: [Bloat] Announcing Flent (formerly netperf-wrapper) v0.10.0 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 May 2015 17:56:07 -0000 Dave Taht 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