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

Allow server-side paging #354

Open
1 task done
mjacoby opened this issue Dec 10, 2024 · 0 comments
Open
1 task done

Allow server-side paging #354

mjacoby opened this issue Dec 10, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@mjacoby
Copy link
Collaborator

mjacoby commented Dec 10, 2024

What is missing?

Currently, the client can basically request the server to send all of its data in a single request which might to in the order of GB or even TB. This might lead to high resource consumption and costs on server-side.
The reason for this is, that a client can set an arbitrary large page size or even non at all.
...

How should it be fixed?

The server should be allowed to limit his response using the paging mechanism.
For example, a client might request submodels with a limit of 100 which would be ~1GB of data. The server then should be able to response with <= 100 submodels as he likes (typically this is done via fixed maximal server page size and/or maximal data size).
For the client to know that he has received less elements than requested, a server should always return the number of elements returned.
...

  • I have signed the required Developer Certificate of Origin (DCO) already.
@mjacoby mjacoby added the enhancement New feature or request label Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant