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

Improve documentation on how Transactions work #1461

Merged
merged 1 commit into from
Aug 3, 2018

Conversation

turt2live
Copy link
Member

Rendered: see 'docs' commit status


The response is based upon various sections of the Synapse code in how it generates a response.

There are no new fields added to the transaction. Originally, previous_ids and pdu_failures were to be documented however neither of these are used in the real world.

The response is based upon various sections of the Synapse code in how it generates a response.

There are no new fields added to the transaction. Originally, `previous_ids` and `pdu_failures` were to be documented however neither of these are used in the real world.
@turt2live turt2live requested a review from a team July 30, 2018 22:59
type: object
description: |-
The PDUs from the original transaction. The string key represents the ID of the
PDU (event) that was processed.
Copy link
Member Author

Choose a reason for hiding this comment

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

Something to consider: we could shorten the response size for massive transactions by assuming that an event not listed here was successfully processed. Synapse and Dendrite both don't seem to care about successful events from the response.

Copy link
Member

Choose a reason for hiding this comment

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

Yup. Though I'm not sure its really worth it, especially if we start limiting the number of pdus per transaction.

Copy link
Member Author

Choose a reason for hiding this comment

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

yea, limiting transaction sizes would be a better solution all around.

@turt2live turt2live mentioned this pull request Jul 31, 2018
35 tasks
@erikjohnston erikjohnston self-assigned this Aug 3, 2018
@turt2live turt2live merged commit d48f1e1 into matrix-org:master Aug 3, 2018
@turt2live turt2live deleted the travis/s2s/transactions branch August 3, 2018 13:38
RiotTranslateBot pushed a commit to RiotTranslateBot/matrix-doc that referenced this pull request Aug 22, 2023
* Move Push Rules section out from Client Behaviour.
* Clarify server vs. client behavior.
* Remove references to unencrypted content.
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

Successfully merging this pull request may close these issues.

2 participants