Comments on: Caching vs. inlining

By: Stoyan

Stoyan — Tue, 15 Dec 2009 17:14:06 +0000

@Michael Hessling – it’s true that it’s likely your components may not make it all the way to 2019, but it’s worth the try. Renaming components is still necessary though, there will be people with the old versions in the cache.

@Denis – yes, one year is fine too. 10 requests in 10 years in not too bad

By: Satya Prakash

Satya Prakash — Sat, 12 Dec 2009 11:37:39 +0000

Good discussion. I hope you will also give information about how to achieve this.
Bing ex. is good. but there I hoped that i will find lots of createElement() for lazy loading. but i could see only one.

By: Michael Hessling

Michael Hessling — Thu, 10 Dec 2009 21:31:40 +0000

“The drawback is, of course, that you cannot modify this file anymore, since some users have already cached it forever and ever till the end of 2019.”

But aren’t most caches size-limited? Won’t your components get pushed out after the user leaves your site and browses to others? When they come back to your site, they’ll have to download your CSS/JS/static stuff all over again. Is changing the name of the asset really all that necessary?

By: Denis

Denis — Thu, 10 Dec 2009 19:12:42 +0000

“HTTP/1.1 servers SHOULD NOT send Expires dates more than one year in the future.”

http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.21

By: Alexsandro

Alexsandro — Thu, 10 Dec 2009 14:33:01 +0000

Great article.
I prefer control this in my scripts by mod_rewrite instead .htaccess.

By: Kyle Simpson

Kyle Simpson — Thu, 10 Dec 2009 13:46:01 +0000

This stuff has been really really good. Keep up the great article topics!