Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AIP-158 page_size fewer than requested #1337

Open
Bu3a3a opened this issue Apr 3, 2024 · 0 comments
Open

AIP-158 page_size fewer than requested #1337

Bu3a3a opened this issue Apr 3, 2024 · 0 comments

Comments

@Bu3a3a
Copy link

Bu3a3a commented Apr 3, 2024

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:

  1. In which cases returning fewer or zero results not at the end of a collection is possible and appropriate?
  2. Doesn't it cause front-end issues? If it does, what approaches are common to prevent them?
  3. 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant