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 7AC1821F25D for ; Sun, 24 May 2015 11:16:39 -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=1432491383; bh=EQ+eRculEvnNvt1MwHHJBSqRAIrin9qnC22WWTo1qlE=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=g+C/x6OXCI5gBLqI13XkRxAaeJTnp1df8RjRulkBCkatPYqv5eP8xdC9NpUdcqXrB Xu0d9kTaDhQk2cy3hzZU1l+MXsXhCC8ol/0tTacb9zqXRG7w3S6V1TFcnwzjsvFccy BwGUSew7tzHrILT1geqlEzU8qu2xMBBLxAgK/zZA= Received: by alrua-karlstad.karlstad.toke.dk (Postfix, from userid 1000) id 4201038BBEB; Sun, 24 May 2015 20:16:22 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Dave Taht References: <877frygk7e.fsf@toke.dk> <87a8wtg8si.fsf@toke.dk> Date: Sun, 24 May 2015 20:16:22 +0200 In-Reply-To: (Dave Taht's message of "Sun, 24 May 2015 11:05:46 -0700") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87y4kdet8p.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 18:17:22 -0000 Dave Taht writes: > well,1) we need a flent-devel mailing list... no need to have this > discussion so widely here.. Yup, will try to set one up soonish. ENOTIME so far. > I agree that *you* do not want to maintain two plotting > implementations inside flent. But: > > I am hugely in favor of various implementations of stuff that can read > the file format and do various (new and interesting) things with it. > The number of python-matplotlib capable developers is small. The > number of javascript capable developers (and web based plotting tools) > is huge. Other means of dealing with the data (postgres json) are also > needed. Oh, sure, quite happy with more implementations. That was option 3. However, until someone actually starts working on such an implementation this is all hypothetical. I'm happy to discuss interoperability issues when such an implementation actually materialises :) > So the json.gz file format WAS readable and translatable by many web > servers and browsers, flent is not (so far as I know, even with adding > a mime type.) Yes, but .json.gz also makes it hard to distinguish from other random gzip'ed json data. I'd rather have a separate file extension for offline storage, and then solve the web problem as a separate problem, which as far as I'm concerned is orthogonal to the encoding of the files on disk. The important thing is the structure of the JSON object, not which compression format and file extension it is stored in. > I liked the original web based prototype, it needed a db back end, but > it seemed like a promising start. And odds are that db back end is going to store the JSON object in its own encoding anyway, hence rendering this whole discussion moot... :) > I don't have a lot of hope for the canvas approach, personally. Too > many abstractions. Yeah, I'm sceptical, but willing to give it the benefit of the doubt if it means I have to write less code... > Personally what I most prefer is that the "expert" implementation be > blazing fast! Yes, well, matplotlib is not exactly a cheetah... -Toke