In the clientPager's nextPage method, there is a check to see if you've already reach the last page or not. requestPager.nextPage should also have this check, to avoid an unnecessary request.
Agreed. A patch would be welcome for this if anyone wants to take it on.
There should also be a check against firstPage in the prevPage method for both pagers.
If we keep calling prevPage() after hitting the first page, the currentPage field will be negative, and we will need to call nextPage() an equal number of times to get back to the first page again. Meanwhile, on the UI, the next page button seems ineffective.