API Usage

Paging or pagination is a process of slicing a certain (usually big and costly) collection into subsets of items in order to improve query performance. Paging is not only a matter of splitting collections into chunks, it also has to consider sorting and filtering. Paging involves the requesting client in specifying a paging request and the responding service to respond with a result set.

In Paging.NET, each paging request is specified in a PagingInfo. The resulting page is returned in a PaginationSet.

• PagingInfo allows to define which page index we want to retrieve (CurrentPage), how many items each page shall contain (ItemsPerPage), how the collection is sorted before it is paged (SortBy resp. Sorting) and if we like to apply a filter (Search resp. Filter) on the target collection.
• PaginationSet sends the subset of Items along with some meta information, like the current page's zero-based index CurrentPage, the total number of pages TotalPages, the total number of items TotalCount (unfiltered: TotalCountUnfiltered).

Contribution

Contributors welcome! If you find a bug or you want to propose a new feature, feel free to do so by opening a new issue on github.com.