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.

Sign up for GitHub

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

Jump to bottom

Define version scheme for appservice endpoints (and fix routes?) #1616

Closed
turt2live opened this issue Aug 30, 2018 · 1 comment
Closed

Define version scheme for appservice endpoints (and fix routes?) #1616

turt2live opened this issue Aug 30, 2018 · 1 comment
Labels
application services wart A point where the protocol is inconsistent or inelegant
Projects
August 2018 r0

Comments

@turt2live
Copy link
Member

Currently the 3rd party stuff uses /_matrix/app/unstable, however by nature application services that have supported this endpoint for the last 4 years are unlikely to be happy about it becoming /v1. We should probably define that /v1 is the correct route and that homeservers fall back to /unstable if they get some sort of error code as a backwards compatibility measure.

Similarly, we should probably put /users, /rooms, and /transactions under the same namespace as 3rd party stuff, using a similar fallback mechanism.

Putting this as an r0 item to spark the discussion.
@turt2live turt2live added wart A point where the protocol is inconsistent or inelegant application services labels Aug 30, 2018
@turt2live turt2live added this to To do (general backlog) in August 2018 r0 via automation Aug 30, 2018
@turt2live turt2live moved this from To do (general backlog) to To do: appservices (prioritized) in August 2018 r0 Aug 30, 2018
@turt2live
Copy link
Member Author

Decided to go with the suggestion in the OP: spec as /v1 and fallback when it errors.

turt2live added a commit to turt2live/matrix-doc that referenced this issue Aug 30, 2018
@turt2live
Version all appservice endpoints and provide a fallback
be5c566 
Fixes matrix-org#1616
@turt2live turt2live mentioned this issue Aug 30, 2018
Merged
August 2018 r0 automation moved this from To do: appservices (prioritized) to Done (this list will be incomplete) Aug 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
application services wart A point where the protocol is inconsistent or inelegant
Projects
No open projects
August 2018 r0
  
Done (this list will be incomplete)
Milestone
No milestone
Development

No branches or pull requests
1 participant
@turt2live