afimrishi

4 ms·

1.
by afimrishi 14y ago
SPDY as specced does not require TLS. However, you can see Google's WebSocket connectivity test results at http://www.ietf.org/mail-archive/web/tls/current/msg05593.ht... . The poor connectivity over ports other than 443 is one of the stro
2.
New TLS Versions(imperialviolet.org)
41 points by afimrishi 14y ago|6 comments
3.
by afimrishi 14y ago
It's worth noting that some common web performance techniques also don't play well with caching. Take a look at http://stackoverflow.com/questions/4791807/data-uris-and-cac... . SPDY server push at least allows the resource to still be nam
4.
by afimrishi 14y ago
I work for Google on Chromium (primarily networking stuff, like SPDY). You can see my comments on this matter here: https://groups.google.com/d/topic/spdy-dev/ipTmn5ty_n0/discu... . "Our plan is to continue what we've been doing: experimen
5.
by afimrishi 14y ago
I think you have someone else in mind. Perhaps one of the commenters on her article?
6.
by afimrishi 14y ago
The original comment in this thread seems to have been deleted, so I can't tell what was said. The primary reasons for implementing our own DNS resolver include: * Being able to fully instrument it. As the article mentions, we have internal
7.
by afimrishi 14y ago
The Chromium experimental DNS resolver should respect that. If it does not, it's a bug and please file it at new.crbug.com.
8.
by afimrishi 14y ago
(I'm the Chromium dev who triaged the bug this morning) This title is misleading. There's a bug when the SSL handshake for a WebSocket encounters an error, such as an invalid server certificate. This obviously sucks for developers, but for
9.
Chromium DNS performance(plus.google.com)
44 points by afimrishi 15y ago|21 comments
10.
by afimrishi 15y ago
- Pipelining would be pretty cool if it worked. There are a number of problems with it: * head of line blocking * transparent proxies that don't support pipelining properly * error detection - FIFO queuing: Why is the client in a bett
11.
by afimrishi 15y ago
That's true for the most part. But if you want to leverage certain SPDY features like SPDY server push, then your app must be SPDY aware. Likewise, if you want to undo normal HTTP optimizations like hostname sharding which are damaging for