Skip to content

[WIP] MSC2300: /ping endpoint#2300

Draft
ara4n wants to merge 1 commit into
old_masterfrom
matthew/msc2300
Draft

[WIP] MSC2300: /ping endpoint#2300
ara4n wants to merge 1 commit into
old_masterfrom
matthew/msc2300

Conversation

@ara4n
Copy link
Copy Markdown
Member

@ara4n ara4n commented Sep 23, 2019

Currently there is no well-defined way for clients to determine whether their server is still alive and well.
Riot/Web fudges this by calling /versions, but this is an abuse (especially if & when /versions becomes a richer endpoint).
Enter /ping instead.

Rendered

@ara4n ara4n added the proposal A matrix spec change proposal label Sep 23, 2019
@ara4n
Copy link
Copy Markdown
Member Author

ara4n commented Sep 23, 2019

#2301 is an example of why we shouldn't be using /versions as a ping endpoint.


## Proposal

Currently there is no well-defined way for clients to determine whether their server is still alive and well.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

why can't they check /sync or other errors? Do we really need a ping endpoint given HTTP has very well-defined errors?

Riot only uses /versions because it got an error on /sync, which it feels is a server problem and therefore tries to reinitialize itself. Hitting /versions on loop is one way of doing this and is a lighter endpoint if there are server performance problems. Theory is, I believe, that when the server starts throwing errors at you it is likely being updated or has its config changed: if it suddenly supports r0.6 then why not use that?

@turt2live turt2live changed the title MSC2300: /ping endpoint [WIP] MSC2300: /ping endpoint Dec 7, 2019
@turt2live turt2live added the kind:feature MSC for not-core and not-maintenance stuff label Apr 20, 2020
@turt2live turt2live marked this pull request as draft April 8, 2021 23:36
@turt2live turt2live added the needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. label Jun 8, 2021
@anoadragon453
Copy link
Copy Markdown
Member

Related: #3360

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:feature MSC for not-core and not-maintenance stuff needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants