You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The API may return fewer results than the number requested (including zero results), even if not at the end of the collection.
To me it seems weird to make N requests to get data. The most 'scary' thing is that number of empty or half-empty responses is unknown beforehand.
Could you explain, please:
In which cases returning fewer or zero results not at the end of a collection is possible and appropriate?
Doesn't it cause front-end issues? If it does, what approaches are common to prevent them?
Doesn't it cause unnecessary/excessive network load in some cases?
I'm trying to comprehend why it's so and how to painlessly work with this restriction. Sorry if the question is newbie. Any answers/links for reading are appreciated.
The text was updated successfully, but these errors were encountered:
Hi!
AIP-158 states:
The API may return fewer results than the number requested (including zero results), even if not at the end of the collection.
To me it seems weird to make N requests to get data. The most 'scary' thing is that number of empty or half-empty responses is unknown beforehand.
Could you explain, please:
I'm trying to comprehend why it's so and how to painlessly work with this restriction. Sorry if the question is newbie. Any answers/links for reading are appreciated.
The text was updated successfully, but these errors were encountered: