General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Announcing Flent (formerly netperf-wrapper) v0.10.0
Date: Sun, 24 May 2015 11:23:00 -0700	[thread overview]
Message-ID: <CAA93jw4bZmrmhMCOjD=0K12EZEn8_unsuAVxgr3bw7g-a22VxA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7K3Umm8=W2M+5AgTk77Jd6W7OqJx3fSG613ausf-WEzw@mail.gmail.com>

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).

  parent reply	other threads:[~2015-05-24 18:23 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
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 [this message]
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='CAA93jw4bZmrmhMCOjD=0K12EZEn8_unsuAVxgr3bw7g-a22VxA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /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