Topic: Fragment caching where content is highly customised

I'm building a site that's for registered users only, and each user will only see the data associated with their account. Think of it like an internet banking site. I expect that they'll hop around pages a bit, viewing data without changing it. Because of that i'm looking at caching. For example the user might look at a list of their current customers, then view the details of the customer, then go back to the list. That's where caching will come in handy.

Read the AWFWR book it looks to me like the default caching mechanism can't deal with this. Am I wrong, or is there another way to do caching?