Feature request: Torso Paginated Collection

[diokey]

When you have paginated REST APIs, It would be nice to have a collection that can be configured to fetch paginated data

var visitCollections = (Torso.PaginatedCollection.extend({
  url: "/visit",
  // define paging configuration
  paging: {
    pageSize: 10,
    pageNumber: 0		
  }
}))();

var visits = visitCollection.createPrivateCollection();
						
visits.getFirstPage();
visits.getLastPage();
visits.getPreviousPage();
visits.getNextPage();
visits.getPage(pageNumber);

We may also want to add sorting

[kentmw]

You've identified the need for the paging to be done on the private collection. That's true. But the paging options should be defined by the private collection as well, as paging is situationally dependent (one form on one page paging with some size and another somewhere else with a different size). Right now, it feels like the api you have for private collections seem pretty good and then if we add the ability to configure page size and a separate url (or GET parameters to narrow the cache's url query) to find the ids it cares about. Now that I've written that out, I think it should always be a different url, because the private collection deals with ids and the cache's url deals with objects.