You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Something that has come up repeatedly in recent WebRTC conferences (San Jose and Paris) is that whilst folks understand and respect the decision to have REST as the only mandatory baseline C-S API, they'd still really really like an optional stream-oriented API of some flavour like Web Sockets to avoid having to poll and potential battery-life/bandwidth implications. And they reason that this optional API should be specified by Matrix to avoid fragmentation.
matrixbot
changed the title
An explicit websocket (or web push) profile for the client-server API
An explicit websocket (or web push) profile for the client-server API (SPEC-81)
Oct 31, 2016
matrixbot
added
the
feature
Suggestion for a significant extension which needs considerable consideration
label
Nov 7, 2016
Something that has come up repeatedly in recent WebRTC conferences (San Jose and Paris) is that whilst folks understand and respect the decision to have REST as the only mandatory baseline C-S API, they'd still really really like an optional stream-oriented API of some flavour like Web Sockets to avoid having to poll and potential battery-life/bandwidth implications. And they reason that this optional API should be specified by Matrix to avoid fragmentation.
So we should do it.
(Imported from https://matrix.org/jira/browse/SPEC-81)
(Reported by @ara4n)
The text was updated successfully, but these errors were encountered: