From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 62FE721F25D for ; Sun, 24 May 2015 11:23:14 -0700 (PDT) Received: by obfe9 with SMTP id e9so42134082obf.1 for ; Sun, 24 May 2015 11:23:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pu03/yYT11Lm5W8StnVr+HUYXUG1nconbwj3NUyVHmE=; b=AMwk1tMW9SH3jVwBhlU9c/5suDtnMADeEEhofvMwZfn1tC1C+/TowpszejHvmD4RCy ARQuKkk6XdfwhTDeU/O+mScssZ+MscdeFoGS32rB7X9j9VH5uECcM+qDH9d54T9n9aSj OeShs3DanGf0gpZWQyATGiV3Y0SfcdtlpGuzhCrz3vBsh2nki1tRLKwUHiHBqPnp3eQl 7aGotdQyqUX4L4/yt2h75+3DytazgTD8EKEHdkWFKfTvLVPTfghZusOJ2e8h+EVdkAYy f3h+Jee/B03mbY8PsxDmnvzqEzXM1x+xg+aeSqtlcURCadH7+C9xwvOZi8k6bIXwwThc 1pQQ== MIME-Version: 1.0 X-Received: by 10.60.147.194 with SMTP id tm2mr14588784oeb.75.1432491780149; Sun, 24 May 2015 11:23:00 -0700 (PDT) Received: by 10.202.105.146 with HTTP; Sun, 24 May 2015 11:23:00 -0700 (PDT) In-Reply-To: References: <877frygk7e.fsf@toke.dk> <87a8wtg8si.fsf@toke.dk> Date: Sun, 24 May 2015 11:23:00 -0700 Message-ID: From: Dave Taht To: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= Content-Type: text/plain; charset=UTF-8 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:23:54 -0000 so far as I know browsers will autonegotiate gzip compression on the wire or in the server. I do not believe (but am woefully out of date on this) bzip can be handled in the browser. http://redmine.lighttpd.net/projects/1/wiki/docs_modcompress http://httpd.apache.org/docs/2.2/mod/mod_deflate.html So my vote is that the native flent format be pure text json (with a mime type mapping it to that) and the default output of flent be flent.gz where it can be automagically decoded when presented with whatever.flent and the .gz file exists instead. And ya still have time to fix it before casting the bzip'd version in stone. I am not big on fixing all the web browsers and servers in the world for "yet another specialized mime type". Even if javacript based decompressors exist for bzip, gzip was the most common format back when i was paying attention (8 years ago).