Well, is a polygon based search, so we may be getting sets of over 10000 (without pagination of course) - that's not really practical to display so my thinking was to simply do a paginated search - retrieve a range (page) of these results, but be able to show the total number of results also (or at least if there are more to be had, even if I cannot get the actual total number).
On the solution of getting all of them and doing pagination in memory - that's certainly an option, but given the large number of results, I'd rather not if the API could help me there - especially since this is a relatively standard pagination scenario - you ask for a range, and the result includes that range and also the total count of the result.
Thanks.
Eugen.