Showing posts with label caching. Show all posts
Showing posts with label caching. Show all posts

Tuesday, September 8, 2009

What changed?

Overheard at a dinner party:

Guest 1: My browser has this feature that remembers what sites I've been visiting, then shows me which ones have changed since I last visited them.

Guest 2: Sounds great.

Guest 1: Yeah, except that most of the time all it means is there are new ads.

Guest 2: Oh.

Guest 1: At least it works with your site, since you don't carry any ads.

(No, the site wasn't Field Notes)

Two similar questions with significantly different answers:
  • Have the bytes representing this page changed?
  • Has this page changed in any meaningful way?
Computers have a pretty good handle on the first but not the second. The bytes can change without the page really changing, not just because of ads but because of trivial reformatting, or an upgrade in some unseen component, or for any of a number of other reasons. Now that everything's all AJAX-y and a page may really just be a script for fetching and displaying the real content, the page can change without the bytes changing.

The questions above are central to web caching, a whole big ball of wax which (to mix metaphors) I'd rather not wade into at the moment. Fortunately, if your job is just to make sure bytes get distributed in an efficient manner you can forget about the second question and concentrate on the first. And a good thing, that, otherwise there would be no Web As We Know It.

If the second question really is important to you, I have one word, son: metadata.

Monday, May 25, 2009

Caching dynamic content

A friend who sells networking equipment, software and such tells me that web caching isn't the big thing it used to be. I didn't press for details, and there was a lot of noise in the room, but I believe his take was that with more content being dynamic, caching made less sense. There's no point caching something that's only going to be accessed in that particular form once. I then mused that the AJAX-y interfaces that tend to come along with dynamic content are designed specifically to hide the same latency that caching tries to reduce.

On the other hand, my friend, being in sales, is probably more interested in how much new stuff is selling than how much is actually deployed. It could just be that the market is more saturated than it used to be.

If only I could be bothered to look up the details ...