3 ms·
Isn't HTTP already a generic messaging and data synchronisation system for the whole web? How will Matrix be anything other than another stack in the field of
by shuntress 9y ago
Isn't HTTP already a generic messaging and data synchronisation system for the whole web?
How will Matrix be anything other than another stack in the field of silos?
Genuine question. I'm not trying to be combative.
Edit: After doing some more reading through the matrix docs, it seems that the goal is to make an extremely easy to implement/setup endpoint that any 'silo' can easily include. This Matrix endpoint will automagically connect to the Matrix endpoint on other 'silos' to facilitate message transfers.
Is this accurate?
- Arathorn 9y agoHTTP itself doesn't give you any standard way to synchronise blobs of real-time data (IMs, VoIP signalling, etc) between servers, or even really between servers and clients. Sure you can write a webapp which uses some combination of long-lived GET, PUT, websockets, HTTP/2 Push etc to 'push' realtime messages around the place, but there's no standard way of doing it; each app makes up its own fragmented and proprietary set of APIs. So Matrix fixes this by defining a standard HTTP API (which can also be used with other RPC transports if you prefer).