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.

Sign up for GitHub

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

Jump to bottom

Spec the implicit limit on /syncs (SPEC-453) #200

Closed
matrixbot opened this issue Sep 11, 2016 · 5 comments
Closed

Spec the implicit limit on /syncs (SPEC-453) #200

matrixbot opened this issue Sep 11, 2016 · 5 comments
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@matrixbot
Copy link
Member

If you call /sync without a filter, or with a filter without a limit, it will use a default limit. We should spec this.

(Imported from https://matrix.org/jira/browse/SPEC-453)
@matrixbot
Copy link
Member Author

Jira watchers: @richvdh

@matrixbot
Copy link
Member Author

matrixbot commented Sep 11, 2016 •
edited
Loading

Links exported from Jira:

relates to matrix-org/matrix-spec-proposals#707

@matrixbot
Copy link
Member Author

Will this be a single generic limit, or a number servers can advertise / communicate to clients?

-- alexander maznev

@matrixbot
Copy link
Member Author

[~pik]: it's a default. There's no need for servers to advertise it to clients.

-- @richvdh

@matrixbot matrixbot mentioned this issue Oct 28, 2016
Closed
@matrixbot matrixbot changed the title Spec the implicit limit on /syncs Spec the implicit limit on /syncs (SPEC-453) Oct 31, 2016
@matrixbot matrixbot added the spec-bug Something which is in the spec, but is wrong label Nov 7, 2016
@richvdh richvdh added clarification An area where the expected behaviour is understood, but the spec could do with being more explicit and removed spec-bug Something which is in the spec, but is wrong labels Nov 7, 2016
@alphapapa alphapapa mentioned this issue Aug 12, 2018
Closed
@turt2live turt2live added the A-Client-Server Issues affecting the CS API label Feb 6, 2019
@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@Cadair Cadair mentioned this issue Mar 14, 2023
Merged
@richvdh
Copy link
Member

richvdh commented Mar 14, 2023

fixed by #1463

@richvdh richvdh closed this as completed Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-Client-Server Issues affecting the CS API clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@turt2live @richvdh @matrixbot