-
Notifications
You must be signed in to change notification settings - Fork 50
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
Should WebTransportSendStream and WebTransportReceiveStream be transferable? #424
Comments
I was hoping to avoid the |
Attempting to transfer On main thread it does seem possible to construct a WebTransport, build a 'complex' readable or writable stream based on it, and then transfer those streams to (distinct) workers. However, so far the performance seems quite bad and it crashes the tab. Sample (which reliably crashes the tab after pressing stop): https://webrtc.internaut.com/wc/wtSender6/ |
Sorry about this. Currently when a stream is transferred, the chunks that are passed through the stream are always cloned, never transferred. Since There was a plan to also support transferring the chunks (see Future Work) but without a concrete use case it never proceeded to the design stage. |
Meeting:
|
For almost a year, between #307 and #395 (nevermind #423), the following streams were transferable streams:
But right now they're not, since "Platform objects can be transferable objects if their primary interface is decorated with the [Transferable] IDL extended attribute."
Q: Should they be? This would allow
.getStats()
to be called where data is read and written, as well as make this allowed:If we don't then the above will fail, and apps would have to work around it like this instead instead:
The text was updated successfully, but these errors were encountered: