matrix-org / matrix-org/matrix-spec
Alternative room transports to full mesh (SPEC-45)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
We shouldn't assume that every room will use full mesh. Ideally rooms should be have configuration along with the policy server explaining how to distribute events amongst the participating servers.
We could have a list of distribution protocols in the room config with two transports that servers MUST support:
1) The current full mesh transport.
2) A simple list of endpoints to pass events to.
Rooms SHOULD support at least one of these two transports. A server can then always join the room by falling back to the simple list of endpoints if it doesn't understand the other federation protocols in the room.
(Imported from https://matrix.org/jira/browse/SPEC-45)
(Reported by @NegativeMjark)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the current full-mesh transport and the room and policy-server configuration in the Matrix specification, then determine how this proposal fits those definitions. Done means the specification clearly defines the supported transport choices, fallback behavior, and room requirements.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100