afimrishi
Re:Introducing SPDY
on Friday June 15, 2012 @11:24AM (#4116959)
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 strongest motivations for real deployments of SPDY over the public internet to require TLS.
Re:SPDY Review by Opera Software
on Thursday June 07, 2012 @09:16PM (#4082185)
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 named (via its URL) so it can be cached and speed up page load times, although goodput may suffer due to unnecessary pushes. This is an area where there are active proposals: https://groups.google.com/d/topic/spdy-dev/TetVOinB-LM/discu....
Re:Firefox 13 Released - Homepage + Speed Improvements
on Tuesday June 05, 2012 @04:21PM (#4070621)
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: experimenting with new ideas in SPDY and recommending the good ones for standardization in IETF (http://tools.ietf.org/html/draft-mbelshe-httpbis-spdy-00). In the end, we only want one protocol, so we don't intend to keep a SPDY track alive longer than a successful standards process."
Out of curiosity, what changes from Speed + Mobility would you like to see in SPDY? We'd love to hear your recommendations on [email protected].
Re:Chrome Networking: DNS Prefetch & TCP Preconnect
on Monday June 04, 2012 @09:17PM (#4066850)
I think you have someone else in mind. Perhaps one of the commenters on her article?
Re:Chrome Networking: DNS Prefetch & TCP Preconnect
on Monday June 04, 2012 @07:22PM (#4066520)
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 debugging pages like about:net-internals, which rely on this instrumentation.
* Being able to run experiments. Google Chrome releases often run A/B experiments to play around with different configurations to see which has better performance and what not. This is harder to do with a 3rd party library.
As Ilya notes, a fuller discussion can be found at the G+ post's comments section.
Note: I'm a Chromium developer on our network stack. I'm also the author of the G+ post linked to in the article.
Re:Chrome Networking: DNS Prefetch & TCP Preconnect
on Monday June 04, 2012 @07:16PM (#4066497)
The Chromium experimental DNS resolver should respect that. If it does not, it's a bug and please file it at new.crbug.com.
Re:Chrome 19 update breaks secure WebSockets
on Wednesday May 16, 2012 @08:25PM (#3984776)
(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 production sites which should not have SSL handshake errors, it should not be an issue.
Chromium DNS performance
Re:SPDY Brings Responsive and Scalable Transport to Firefox 11
on Tuesday February 07, 2012 @11:52PM (#3565107)
- 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 better position to know in what order the page needs to be rendered than the server? Isn't the server the one that knows all the resources that need to be sent to the client?
- Client initiated request: Yeah, server push is a complicated area. But there are some cases where server push is clearly superior. For example, data URI inlining ruins cacheability. It's better to server push an already cached resource that can be RST_STREAM'd than inline a resource and make it larger and uncacheable.
- While we'd like to get rid of headers as much as possible, it's still impractical to completely eliminate headers like User-Agent.
- SPDY does not force data compression, and optional data compression has been removed in draft spec 3.
Re:Twitter adds SPDY support to Netty
on Tuesday February 07, 2012 @11:34PM (#3565052)
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 SPDY, your app should be SPDY aware. Check out http://dev.chromium.org/spdy/spdy-best-practices for other recommendations.