Streaming file transfers #432
Labels
A-Client-Server
Issues affecting the CS API
feature
Suggestion for a significant extension which needs considerable consideration
Once upon a time, before Matrix, we had a glorious feature of streaming file transfers - where one client would HTTP POST the file using Range headers as the other would HTTP GET it with Range headers also. It worked surprisingly well; good enough to livestream video and do low-latency push-to-talk whilst leaving copies of files on the media repo.
It'd be nice one day to have this in Matrix too. This would mean ensuring that we can send events before the media has finished up loading.
The text was updated successfully, but these errors were encountered: