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

MSC3982: Limit maximum number of events sent to an AS #3982

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

Half-Shot
Copy link
Contributor

@Half-Shot Half-Shot commented Mar 21, 2023

@Half-Shot Half-Shot changed the title MSCXXXX: Limit maximum number of events sent to an AS MSC3982: Limit maximum number of events sent to an AS Mar 21, 2023

- This requires a two way communication between the Homeserver and AS, which presently isn't required.
- This potentially costs more time in negotiation than any efficiency losses from the hardcoded limit.
- Practically speaking, Synapse [has had a limit of 100](https://github.com/matrix-org/synapse/blob/develop/synapse/appservice/scheduler.py#L85-L86)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For other homeserver implementations:

Comment on lines +53 to +54
Potentially the homeserver and application service could negotiate a maximum event size instead of specifying
one in the spec, however this isn't desirable because:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another reason this is not reasonable is that neither Synapse nor the application service know about any middle boxes between them, so neither of them can possibly know the maximum HTTP request size that is allowed without trial & error.

@turt2live turt2live added proposal A matrix spec change proposal application services kind:maintenance MSC which clarifies/updates existing spec needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. labels Mar 21, 2023
@Half-Shot
Copy link
Contributor Author

Synapse seems to implement this already, so I think needs-implementation can go away.

@turt2live turt2live removed the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Apr 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
application services kind:maintenance MSC which clarifies/updates existing spec proposal A matrix spec change proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Appservice API /_matrix/app/v1/transactions/ should specify maximum transaction sizes
3 participants