3 ms·
> Doing so is probably a bad idea, since when new content gets added, the contents of a specific index pagination will change unless you paginate in chronologi
by leeoniya 7y ago
> Doing so is probably a bad idea, since when new content gets added, the contents of a specific index pagination will change
unless you paginate in chronological order rather than reverse chronological. but no one does.
- efreak 7y agoIt's easy enough. Just request the next X results after the last result on the current page, like so: `?resultsperpage=50&resultsafter=postid750`. If you're not sorting by time, then you should be able to add a time constraint to the search backend and include that parameter as well. I've also seen forums that cache the results for a certain amount of time, and only return the search ID and page number in the query string.