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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: