igrigorik

12 ms·

91.
by igrigorik 13y ago
Effectively, you're describing socket pooling and re-use.. across sessions / tabs / windows. Most browsers already have this in place. :) Some details on Chrome implementation here: http://www.igvita.com/posa&
92.
by igrigorik 13y ago
The goals section in the design doc provides a high-level comparison (and motivation behind "why QUIC"): https://docs.google.com/document/d/1RNHkx_VvKWyWg6Lr8SZ-saqs...
93.
by igrigorik 13y ago
TCP is not going away anytime soon... If anything, the hope is that QUIC can help improve TCP in the long run -- but first, we need to validate a lot of the design assumptions. :)
94.
Experimenting with QUIC(blog.chromium.org)
102 points by igrigorik 13y ago|13 comments
95.
Innovating with HTTP 2.0 Server Push(igvita.com)
9 points by igrigorik 13y ago|0 comments
96.
by igrigorik 13y ago
A comparison of the different hints, and which browsers support them: http://chimera.labs.oreilly.com/books/1230000000545/ch10.htm...
97.
by igrigorik 13y ago
I'm not even sure what side effects "display: none" would have here.. But that's beside the point. The point of prerendering is to to deliver an instant "swap" of the prerendered tab when the user navigates to that page - think of it as a h
98.
by igrigorik 13y ago
Yep, that's how it's implemented.
99.
by igrigorik 13y ago
You can see if pre-rendering is being triggered in chrome://net-internals#prerendering. See: http://www.igvita.com/posa/high-performance-networking-in-go... And "yes": https://www.evernote.com/shard/s1/sh/0f3592b8-d72c-40f7-9bbf...
100.
by igrigorik 13y ago
Correct on both counts.. Pre-fetching DNS names for origins not on the page is, indeed, a nice use case - redirects are a good example. Similarly, embedding a <link rel=dns-prefetch> in the head will trigger an early DNS lookup, whi
101.
by igrigorik 13y ago
http://chimera.labs.oreilly.com/books/1230000000545/ch10.htm... Scroll down for list of browsers (and versions) that support prefetch / prerender / and other hints.
102.
by igrigorik 13y ago
Yep. Prefetch != prendering. Prefetch only fetches the single resource, and is meant as a "post load" hint. Whereas prerendering fetches the entire page, and all of its assets. http://chimera.labs.oreilly.com/books/1230000000545/ch10.htm..
103.
Deploying WebP via Accept Content Negotiation(igvita.com)
4 points by igrigorik 13y ago|0 comments
104.
by igrigorik 13y ago
Yep, it'll concatenate files, minify them, etc., all the things you would expect. Perhaps the only caveat is: it doesn't do any dependency management, etc., which sprockets provides (if you actually use that part of it).
105.
by igrigorik 13y ago
Yup, in fact, that's exactly how ZippyKid integration is setup: https://www.zippykid.com/2013/04/23/partnership-with-google-... It doesn't matter if the files are local or remote, ngx_pagespeed can fetch from both. Some docs on related fu
106.
by igrigorik 13y ago
You can see the complete list of filters (40+) here: https://developers.google.com/speed/docs/mod_pagespeed/confi... Note that docs above are for mod_pagespeed (Apache), but all of the same filters are available in nginx port as well - it
107.
by igrigorik 13y ago
Actually: https://chromiumcodereview.appspot.com/13814024 :-)
108.
by igrigorik 13y ago
This is slightly orthogonal, but still worth mentioning: there is WebP codec available for Windows, which adds WebP support in explorer and all the other common tools. Download page: https://developers.google.com/speed/webp/download
109.
by igrigorik 13y ago
We just landed "image/webp" in Accept header in Chrome, behind a flag.. Opera already advertises WebP support in their Accept header. So, with that in place, it should make things a lot simpler (although it doesn't solve the Save As case).
110.
by igrigorik 13y ago
A good discussion on this here: https://groups.google.com/a/chromium.org/forum/#!msg/chromiu...
111.
Chrome DevTools can do THAT? Part II(docs.google.com)
3 points by igrigorik 13y ago|1 comments
112.
Say no to reimplementing the browser's parser in JavaScript(plus.google.com)
1 points by igrigorik 14y ago|0 comments
113.
by igrigorik 14y ago
Yep, tips for where and how to engage with the project: http://www.chromium.org/blink#participating
114.
HTTP 2.0 - draft 2(tools.ietf.org)
2 points by igrigorik 14y ago|0 comments
115.
by igrigorik 14y ago
https://chromium.googlesource.com/chromium/blink
116.
by igrigorik 14y ago
cough web components cough
117.
by igrigorik 14y ago
Starting today new dev work will go into Blink repo. So, effectively, today.
118.
by igrigorik 14y ago
Not at all. iOS version uses UIWebView, but all the rest is Chrome code.
119.
by igrigorik 14y ago
Nope, no changes for Chrome for iOS: current version already uses UIWebView and will continue to do so. The rest of the infrastructure (networking, etc), is Chrome code.
120.
Faster, smaller and more beautiful web with WebP(igvita.com)
3 points by igrigorik 14y ago|0 comments

More ›