The easiest option I can suggest is to use memcache to store the
'bookmarks' for the beginning of each page. If the user wants the 5th
page, for example, you can look in memcache for the '5th page'
bookmark (which is a tuple (score, key) for the first entity that
should appear on the page, or the
>
> The primary purpose is a user may want to go back several pages just
> to
> see what's there.
This is what I figured - so then, instead of selecting 11 stories at a
time, select say, 51 stories, adjust the offset accordingly, and the
user can navigate to the next/prev 3 pages. Or up it
The primary reason I'd like the specific page number capability is for
the format I'm going with, it's something users expect to see. Though,
currently it looks like this is not going to be a possibility. The
primary purpose is a user may want to go back several pages just to
see what's there.
I
Out of interest, why is it a requirement that you can page to any
arbitrary page? How would a user know that they want to go to page 5
specifically?
How about just letting them go to a page in the next/prev n pages,
where n is, say, 3 - as well as the last and first pages.
More on this her
I've spent quite a long time looking in to it, and I was unable to
come up with a solution that didn't involve operations that either
timed-out or came perilously close. I'll be personally in awe of
whoever comes up with an approach that makes it work.
--~--~-~--~~~---
