matrix-org / matrix-org/matrix-spec
Client-Server should use "Accept" header to allow clients to request other encoding types
Open
Nobody has claimed this yet.
A-Client-Server
feature
- Dominant language
- HTML
- Stars
- 330
- Forks
- 150
- Avg merge
- 2h 21m
- Merged PRs (30d)
- 3
Description
This would be nice as a future-proof way to allow home servers multiple options in terms of encoding. For example, you could use this to ask for msgpack, bson or json format responses and get the best option from it.
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
Review the Matrix client-server specification's current response encoding rules and how the Accept header could express requests for msgpack, bson, or JSON. Define the encoding-selection behavior and document which responses and fallback rules are covered; done means the specification clearly explains how clients request and servers choose an encoding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100