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

Add support for 206 partial content #2

Open
alhoo opened this issue Mar 9, 2022 · 1 comment
Open

Add support for 206 partial content #2

alhoo opened this issue Mar 9, 2022 · 1 comment

Comments

@alhoo
Copy link

alhoo commented Mar 9, 2022

Current implementation pushes the whole video in one request. This can be problematic in many serverless environments, due to payload size limitations.

Using the 206 partial content http responses we could allow unlimited video size. The video player is able to handle 206 responses which makes them very suitable for our use case.

The core idea is to check if the response size is larger than a limit (for example 1MB) and only return content up to that limit. The server must also indicate that it is a 206 partial content and set the Content-range headers accordingly. This will cause the client to ask for more content using the Range header. Server must also then handle the Range selection correctly.

@giacomocerquone
Copy link
Owner

this is very interesting yet I've never implemented such a thing. Would you mind opening a pr to at least provide a POC of this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants