W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2012

Re: Ascii-based SPDY "compression" idea

From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Mon, 02 Apr 2012 13:17:51 +0000
To: (wrong string) ™ˆ™˜Œ) <willchan@chromium.org>
cc: Peter Lepeska <bizzbyster@gmail.com>, ietf-http-wg@w3.org
Message-ID: <2614.1333372671@critter.freebsd.dk>
In message <CAA4WUYg79y39s3M=NpuUSATJQGSFJvE_PKz+rW3ZGeWbUkcQjg@mail.gmail.com>
, =?UTF-8?B?V2lsbGlhbSBDaGFuICjpmYjmmbrmmIwp?= writes:

>It's unclear to me the point that you're making. Above, Peter said "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." to which
>you said "I think that is an unwarranted assumption."
>
>So, just to clarify, we're on agreement that all GETs are being routed to
>the same HTTP router, right?

Yes, they go to the same HTTP router, but very likely different
HTTP servers.

I strongly belive that we need to recognize HTTP routers as a class
in HTTP/2.0, a class semi-distinct from the more general proxy,
because they handle the biggest bandwidths and look at the smallest
parts of the HTTP headers.

Proxies with more functionality, caching or filtering for instance
by definition needs to look at more of the metadata becuase they
are, at some level, involved in the semantics.

But the basic HTTP-router just needs to figure out which webserver
this goes to and the primary criteria seems to be:
	Host:
	URI pattern match
	session-cookie
in that order.

-- 
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 13:18:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:59 GMT