Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
akalin
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
17 ms
·
151.
▲
by
akalin
13y ago
Thanks for the feedback! In my defense, I can only say that I was a less-experienced coder when I wrote that. :) The comments were intended to extend the preceding prose explanation rather than being comments per se. The actual code is not
152.
▲
by
akalin
13y ago
Re. multiplexing at the HTTP layer, because an HTTP replacement has to be deployable and testable. However, now that the ideas in SPDY have been proven and are on their way to being standardized, you can look at QUIC to see what can be done
153.
▲
by
akalin
13y ago
Re. Patrick's sentence, you're right, but as I mentioned above, SPDY/4 will become HTTP/2 (we're working through the standardization process). So I think most of the major players are on board with "fixing"
154.
▲
by
akalin
13y ago
I didn't have to look hard to find bug reports for pipelining. An example is https://bugs.launchpad.net/ubuntu/+source/apt/+bug/948461 for Amazon's S3. I'd be interested if the problem is
155.
▲
by
akalin
13y ago
What is the caution?
156.
▲
by
akalin
13y ago
HTTP pipelining is turned off by default in most browsers due to concerns with buggy proxies and servers (see https://bugzilla.mozilla.org/show_bug.cgi?id=264354 ). It may work for you and the particular set of servers you
157.
▲
by
akalin
13y ago
Disabling gzip compression isn't the only workaround to the CRIME attack. For Chromium, Adam Langley patched zlib to differentiate between various classes of data; see https://code.google.com/p/chromium/issues