[eluser]atlas7[/eluser]
The silent paging technique seems promising, thanks. However, each call to the view will only send a partial page, right? So the controller will first have to call a view to send the initial part of the page (doctype, head, header, etc.), then it will call the view with each set of rows as in your example, and then finally it will have to call the view to tell it to display the rest of the page.
I can see this getting quite messy. The controller now has to have knowledge about how the page is being constructed, and this defeats the MVC separation.
Perhaps the controller should send a list of indices to the view, and the view should then call the model to get the data items corresponding to the indices and display them.
I would be very interested in seeing examples of how any of this has been cleanly implemented by anybody else.