| http://en.oreilly.com |
756 |
| http://www.bsdmap.com |
446 |
| http://www.slideshare.net |
82 |
| http://cache.baidu.com |
9 |
| http://dancroak.com |
6 |
| http://207.46.192.232 |
4 |
| http://wew.bsdmap.com |
4 |
| http://httpwww.bsdmap.com |
4 |
| http://web.mail.bsdmap.com |
3 |
| http://yaoge123blogwww.bsdmap.com |
2 |
| http://w3ww.bsdmap.com |
2 |
| http://translate.googleusercontent.com |
2 |
| http://www.linkedin.com |
2 |
| http://www.zhuaxia.com |
1 |
| http://static.slidesharecdn.com |
1 |
| http://www.bsdmap.com. |
1 |
| http://http.bsdmap.com |
1 |
| http://webcache.googleusercontent.com |
1 |
| http://awww.bsdmap.com |
1 |
| http://ww.bsdmap.com |
1 |
1–1 of 1 previous next
This talk is not really about Rack::Cache.
There's so many different caching systems.
Wire level
Declarative.
Don't worry if this doesn't look familiar.
People are most familiar with. When we think about HTTP caching, this is what comes to mind.
Bandwidth/Traffic Reduction.
Number of Clients served by the Cache.
I don’t want to talk about Client caches.
Things are good for, like, a year.
Ramble about research guys trading papers and linking to each other.
Netscape goes public in 1995
Roughly 2.3KB/s
Today, yahoo.com homepage is 388K - 2m48s
JavaScript - didn’t exist.
So what was the most important issue to solve?
Last-Modified
ETag
Do less work.