You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It currently supports one notification but there is some evidence to suggest it would be more efficient to deliver these in bulk transaction-like requests.
The text was updated successfully, but these errors were encountered:
This has interactions with how we manage reliability of push when sygnal is unreachable, or restarted while processing a push request:
Currently synapse makes no attempt to resend pushes which don't get a successful response from sygnal; however that obviously leads to unreliability. Assuming we wanted to fix that, we might need to give pushes transaction ids so that sygnal can de-duplicate. We should consider how we would extend that to transactions which contain multiple pushes. (Although a simple mechanism would be just to give each push within a transaction its own ID.)
Technically speaking, it supports sending the same notification to multiple devices at a time, via the devices parameter. That said, it's not currently used. It's of vague interest for MSC3013 which would make it totally useless.
richvdh
transferred this issue from matrix-org/matrix-spec-proposals
Mar 1, 2022
It currently supports one notification but there is some evidence to suggest it would be more efficient to deliver these in bulk transaction-like requests.
The text was updated successfully, but these errors were encountered: