-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Conversation
Can one of the admins verify this patch? |
2 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Hi any updates planned in the future? /me hopes this would be a better alternative for Android without GCM than doing requests every few minutes. |
See also matrix-org/matrix-js-sdk#461 for the js-sdk side of this. I realised that we've only fed back in #riot-dev and #matrix-dev on this, but for the record: the work here looks really good. I'm still unclear on how much of a benefit WS is actually providing (in terms of bandwidth usage or latency) as per matrix-org/matrix-js-sdk#461 (comment), and we haven't had bandwidth to evaluate it ourselves, otherwise we might be in a position to prioritise it higher. However, we otherwise simply don't have bandwidth in the core team to shepherd it through currently - we are putting all our effort into fixing synapse's core stability problems and getting the spec to a 1.0 (and synapse to a 1.0) rather than adding new features. So either it needs to be clearly a massive improvement, or we need someone else to step in and review it and benchmark it and make the case for prioritising it. Sorry that it's got stuck for so long :( |
To add to what matthew said: it's not just about shepherding this into synapse. Even if it did make a big improvement, it's rare that something substantial like this lands and immediately integrates perfectly with other software, so we'd have to budget for some time to handle any issues that might come up. I'm very keen that we don't get distracted into bug-fixing of new features rather than stabilising what we have. |
Your mentions are valid. I started this websocket project as POC because people were asking for this. |
…telist_login_fallback Always whitelist the login fallback for SSO
* Don't show the login forms if we're currently logging in with a password or a token. * Submit directly the SSO login form, showing only a spinner to the user, in order to eliminate from the clunkiness of SSO through this fallback.
… fix log-output in a special case - when synapse was run via a terminal where utf8 is not possible/enabled but there is an utf8-character send, the output causes an Exception
- fix ref-errors - handle presence at init to not show the user as offline all the time while beeing connected
- now the presence-state will reset to known presence on every method which will be used when the user is online - although he has set to appear as offline
- do not set the presence on each request but instead "just bump" the presence time when a new event (caused by manual interaction) gets received - remove usage of unneeded lambda terms - rename "content" to "params" to be consistent to other _handle_*() - throw SynapseError(400) instead of KeyError when more than allowed params were passed
- enable websocket-endpoint by using ressource "websocket" - enable compression based on config - make use of remote host (or x-forwarded-for) (based on config)
Some debug tools I have found do not allow setting a WebSocket protocol. To be able to use them evaluate the parameter and only throw an Exception (which leads to socket termination) when a not-allowed protocol is passed (currently all beside "m.json") Default: m.json in case no protocol was specified
- avoid usage of self.factory
Any updates? This feature might decrease network traffic consumption, so it will utilize low network bandwidth cases better. Also:
|
sadly, given we haven't found time to merge this in 4.5 years, I can't see that situation changing any time soon, so I'm going to go ahead and close it. |
Would like to see this merged |
This is my working version for websocket support in synapse.
websocket
" as ressourceExample config to enable Websocket which shall be reverse-proxied can look like:
Signed-off-by: Matthias Kesler [email protected]