Re:Why we don’t use a CDN: A story about SPDY and SSL (2014)
by jmkni on Thursday April 02, 2015 @07:45AM
(#9310017)
Aren't they also useful because if you and I use the same CDN for our libraries, we both use the same library/version, and a user visits my site and then visits your site, the libraries are already cached in the browser? If we both store those libraries locally, the library is loaded twice.
That's my understanding of it anyway.
Re:Why we don’t use a CDN: A story about SPDY and SSL (2014)
by eli on Thursday April 02, 2015 @08:26AM
(#9310208)
Yes, though there's some debate as to how often this actually matters. A surprisingly large number of the general web public comes in with a completely cold cache.
Re:Why we don’t use a CDN: A story about SPDY and SSL (2014)
by michaelmior on Thursday April 02, 2015 @09:35AM
(#9310563)
Very often people concatenate and minify different assets, which is another reason that this sharing doesn't occur much in practice.
Re:Why we don’t use a CDN: A story about SPDY and SSL (2014)
by riskable on Thursday April 02, 2015 @12:43PM
(#9311801)
...which creates another problem with optimization: As soon as you make a change--no matter how small--to a single one of those concatenated assets you now have to deliver the entire new combined asset to the client. If you make changes to your JS/CSS assets on a regular basis (rapid iteration anyone?) this means your clients might be best served via individual assets (depending on your traffic patterns).
I have solved this problem myself by avoiding concatenation and using the browser's IndexedDB to store assets that can be loaded dynamically (JS, CSS, and client-side templates). Assets like this get downloaded over a WebSocket connection which provides the same advantage of SPDY in that no re-negotiation is necessary.
You can see the implementation of this here:
https://github.com/liftoff/GateOne/blob/master/gateone/core/...
...and the client side code is here:
https://github.com/liftoff/GateOne/blob/master/gateone/stati...
(Including the functions immediately following that one)
Re:Why we don’t use a CDN: A story about SPDY and SSL (2014)
by TheLoneWolfling on Thursday April 02, 2015 @08:25AM
(#9310203)
This is where links that have a hash would be useful.
(I.e. "This links points to this file - if you already have the file with this hash use it instead")
CDNs are useful because they load content closest to where the user is located.