On 01/02/2014 11:19 PM, Matthew Flaschen wrote:
This doesn't seem like a great use case. Almost any realistic pager is going to have too much data to send it all to the client. This even includes a pager of all the revisions of a single article (a lot of pagers in MW have far more pages than that).
That means the paging has to be done server side anyway.
Sorry, I should have been more clear. The part about selecting rows (e.g. an API call that returns the right 100 rows, based on which page you're on/start position) generally has to be on the server. But it could return a 100-element JSON array and let a client-side template engine render that.
Matt Flaschen