Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Richard Brown <richard.e.brown@dartware.com>
To: Maciej Soltysiak <maciej@soltysiak.com>
Cc: Richard Brown <richard.e.brown@dartware.com>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Bufferbloat at LUG talk - Meeting Report
Date: Mon, 10 Dec 2012 00:16:29 +0000	[thread overview]
Message-ID: <54532012A5393D4E8F57704A4D55237E3CE5E001@CH1PRD0510MB381.namprd05.prod.outlook.com> (raw)
In-Reply-To: <CAMZR1YCbqcjgR9wzeh-GaJ_0KqtPoKmtLefvhsMyibkN5FjUWA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]

Hello Maciej,

Thanks for the kind words about my presentation.

Your imagined dialog is spot on. It's a good way to let people recognize this common situation, and what the fix might be.

Best regards,

Rich

On Dec 9, 2012, at 12:32 PM, Maciej Soltysiak <maciej@soltysiak.com<mailto:maciej@soltysiak.com>> wrote:

Excellent job Richard! Those slides are very clean and informative and you got fantastic real life user reports!
Point #1 is very common: lots of behind-the-scenes javascript, buffering, asynchronous requests, facebook chat box and updates, etc.

I was trying to make a mock conversation for the purpose of providing a story backing up the debloating efforts so that end users realize better what's going on. Please, guys, have a look and comment:
https://soltysiak.com/wiki/index.php/BB_dialog

Part 1 is an intro, also touching on tiered ISP services. Part 2 would be what bufferbloat is all about. Part 3 is an outro to have the users have a take-home message, also touching on DPI and other evil stuff ISPs do trying to workaround the issues.

You can edit that wiki.

I couldn't post it on bufferbloat.net<http://bufferbloat.net/> wiki because I don't seem to have privilege to create new pages so I setup my own.

Regards,
Maciej


[-- Attachment #2: Type: text/html, Size: 1906 bytes --]

      reply	other threads:[~2012-12-10  0:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4092.1353748990.1742.cerowrt-devel@lists.bufferbloat.net>
2012-11-26  1:11 ` [Cerowrt-devel] Bufferbloat at upcoming LUG talk Richard Brown
2012-11-26 11:49   ` Dave Taht
2012-11-26 15:37     ` Jim Gettys
2012-11-26 12:26   ` Michael Richardson
2012-11-26 14:00     ` Dave Taht
2012-11-26 15:28       ` Michael Richardson
     [not found] ` <A2E41EFF-2507-457D-9086-06E718192D22@intermapper.com>
2012-12-09 16:56   ` [Cerowrt-devel] Bufferbloat at LUG talk - Meeting Report Richard Brown
2012-12-09 17:32     ` Maciej Soltysiak
2012-12-10  0:16       ` Richard Brown [this message]

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54532012A5393D4E8F57704A4D55237E3CE5E001@CH1PRD0510MB381.namprd05.prod.outlook.com \
    --to=richard.e.brown@dartware.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=maciej@soltysiak.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