Viewing profile — afimrishi

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 poo…

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... . SP…

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... …

I think you have someone else in mind. Perhaps one of the commenters on her article?

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 fu…

The Chromium experimental DNS resolver should respect that. If it does not, it's a bug and please file it at new.crbug.com.

(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 serve…

- 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…

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 …