Justin James wrote:
- Few data expected and fresh data is required: go with J.Ja. solution;
- Large amounts of data and fresh data is not required: go with a local database cache;
- Large amounts of data and fresh data is required: the 3rd party needs to implement pagination, unless it’s impossible. BTW: you’re getting unreasonable requirements. Run away!)
You could still paginate if you did a bit of work. There are methods to pull the requested page number, and number of records per page, if you look at the scaffolding-created actions you will see how it works. You could use that to pass to the REST API. You *may* need to inject fake records into the results list before the current page to pad it out, if memory serves.
J.Ja
Indeed. Still, it really depends on the amount of records, and how fresh your data needs to be.J.Ja
- Few data expected and fresh data is required: go with J.Ja. solution;
- Large amounts of data and fresh data is not required: go with a local database cache;
- Large amounts of data and fresh data is required: the 3rd party needs to implement pagination, unless it’s impossible. BTW: you’re getting unreasonable requirements. Run away!)