-
Notifications
You must be signed in to change notification settings - Fork 27
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
Pass pullAlgorithm
while initializing [[readable]]
?
#187
Comments
Right, there is a mismatch here. The intent was to use the start algorithm that would basically wait for a frame to be available and enqueue it as soon as available, independently on the actual queue size or whether pull was called (no backpressure like on writer side). We should revise this section to align and could use readEncodedData as part of pulling data. Maybe we could revise the back pressure mechanism here, depending on what UAs actually do (Safari has no back pressure here). |
Sounds also like it could be helped by setting highWaterMark to infinity, as doing so will start pulling immediately and indefinitely. |
…a promise. Set the highWaterMark to Infinity to keep the same behavior (no backpressure) and add a note about this. Fixes w3c#187.
…a promise. Set the highWaterMark to Infinity to keep the same behavior (no backpressure) and add a note about this. Fixes w3c#187.
…a promise. Set the highWaterMark to Infinity to keep the same behavior (no backpressure) and add a note about this. Fixes w3c#187.
https://w3c.github.io/webrtc-encoded-transform/#stream-creation
But it defines no pullAlgorithm, and nothing explicitly calls
readEncodedData
outside the stream, which means nothing will enqueue any data at all. Should it pass a pullAlgorithm that calls readEncodedData?The text was updated successfully, but these errors were encountered: