Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streaming file transfers #432

Open
ara4n opened this issue Feb 14, 2019 · 4 comments
Open

Streaming file transfers #432

ara4n opened this issue Feb 14, 2019 · 4 comments
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration

Comments

@ara4n
Copy link
Member

ara4n commented Feb 14, 2019

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.

@ara4n
Copy link
Member Author

ara4n commented Feb 14, 2019

related (but not the same): #189

@turt2live turt2live added feature Suggestion for a significant extension which needs considerable consideration A-Client-Server Issues affecting the CS API labels Feb 15, 2019
@ShadowJonathan
Copy link
Contributor

Related matrix-org/synapse#4780

@richvdh richvdh transferred this issue from matrix-org/matrix-spec-proposals Mar 1, 2022
@ShadowJonathan
Copy link
Contributor

Also related, given that MSC4016 has been proposed; MSC3469 aims to solve this problem in current Matrix, by giving the assurance to clients that they can send HTTP Range: requests to media endpoints, and get chunked responses.

@ara4n
Copy link
Member Author

ara4n commented Jan 4, 2024

MSC3469 doesn't solve the problem of streamed uploads (or E2EE streaming), which MSC4016 addresses.

I've done an initial implementation at matrix-org/matrix-encrypt-attachment#26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Client-Server Issues affecting the CS API feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

3 participants