- From: 陈智昌 <willchan@chromium.org>
- Date: Mon, 2 Apr 2012 12:13:10 +0200
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>
- Cc: Peter Lepeska <bizzbyster@gmail.com>, ietf-http-wg@w3.org
Received on Monday, 2 April 2012 10:13:39 UTC
On Mon, Apr 2, 2012 at 2:11 AM, Poul-Henning Kamp <phk@phk.freebsd.dk>wrote: > In message < > CANmPAYH38bbDJtcDLxoHcTSZ06685M30LC9DP7bMcUoJu5j4ig@mail.gmail.com> > , Peter Lepeska writes: > > >Since a SPDY session is associated with a single TCP connection, we can > >assume all GETs on that connection are being routed to the same web > server. > > I think that is an unwarranted assumption. > > Many sites today will deliver static content like images from one > set of servers and dynamic content from another (typically larger) > set of servers, and some kind of "http-router" will split the > requests on the TCP connection up between them. > Just to be clear, is this "http-router" a reverse proxy that terminates the TCP connection and forwards HTTP requests onward to backend application servers? Because if so, then I think the core of Peter's point still stands. The "http-router" can handle all the header compression/decompression for SPDY. > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > >
Received on Monday, 2 April 2012 10:13:39 UTC