From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] Google's experiments with QUIC and SPDY
Date: Fri, 28 Jun 2013 01:33:22 -0700 [thread overview]
Message-ID: <20130628083322.D07BE406064@ip-64-139-1-69.sjc.megapath.net> (raw)
Has anybody tried this stuff in a bloat sensitive environment?
Experimenting with QUIC
http://blog.chromium.org/2013/06/experimenting-with-quic.html
"QUIC (Quick UDP Internet Connections) is an early-stage network
protocol we are experimenting with that runs a stream multiplexing
protocol over a new flavor of Transport Layer Security (TLS) on top of
UDP instead of TCP. QUIC combines a carefully selected collection of
techniques to reduce the number of round trips we need as we surf the
Internet. You can learn more in the design document, but here are some
of the highlights: ..."
SPDY: An experimental protocol for a faster web
http://www.chromium.org/spdy/spdy-whitepaper
As part of the "Let's make the web faster" initiative, we are experimenting
with alternative protocols to help reduce the latency of web pages. One of
these experiments is SPDY (pronounced "SPeeDY"), an application-layer
protocol for transporting content over the web, designed specifically for
minimal latency. In addition to a specification of the protocol, we have
developed a SPDY-enabled Google Chrome browser and open-source web server. In
lab tests, we have compared the performance of these applications over HTTP
and SPDY, and have observed up to 64% reductions in page load times in SPDY.
We hope to engage the open source community to contribute ideas, feedback,
code, and test results, to make SPDY the next-generation application protocol
for a faster web.
--
These are my opinions. I hate spam.
next reply other threads:[~2013-06-28 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 8:33 Hal Murray [this message]
2013-06-28 16:33 ` Stephen Hemminger
2013-06-28 16:57 ` Dave Taht
2013-06-28 17:48 ` Dave Taht
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=20130628083322.D07BE406064@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--cc=bloat@lists.bufferbloat.net \
/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