New API Pagination - Performance Degradation
The pagination requirement in the upcoming API release requires multiple API calls in place of one.
I did a test integration on one of our custom javascript operations that queries events and currently returns about 1300 records, which takes about 2 seconds (already slow by modern standards - by the way I am running a very fast internet connection). With the limitation of 100 records per query, it now requires 13 iterations at 2 seconds a piece for a total of just under 30 seconds. This is obviously unacceptable.
I have attached a code snippet to illustration what I am doing.
Unless I am doing something wrong, this will result in the Wild Apricot product being unusable.
Have any other developers out there run into the issue?