I was working on a caching problem and it reminded me that caching requests for a resource with standard pagination sucks. You cache Page 1 with some set of ob

I was working on a caching problem and it reminded me that caching requests for a resource with standard pagination sucks. You cache Page 1 with some set of objects, by the time you cache Page 2 you have Page 2 of a different overall set. It's inconsistent and wonky. I was hoping there was a more clever way to tease out an elegant solution here.