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

Make DataChannels Transferable and explain the implications #445

Closed
wants to merge 1 commit into from

Conversation

ekr
Copy link
Contributor

@ekr ekr commented Dec 29, 2015

@stefhak
Copy link
Contributor

stefhak commented Dec 29, 2015

The actual transfer algorithm is not described. Look at e.g. https://html.spec.whatwg.org/multipage/scripting.html#transferCanvasProxy or https://html.spec.whatwg.org/multipage/comms.html#transferMessagePort (the transfer for ArrayBuffer also describes some error handling for the case when the ArrayBuffer was already neutered).

@alvestrand
Copy link
Contributor

Tagging @annevk because I think the comment originated from him.

@annevk
Copy link
Member

annevk commented Jan 7, 2016

Yeah, you will need to define what transferring actually means (presumably you create a new instance within the other realm and move some internal slot) and how it affects the original object (presumably some operations will start failing). whatwg/html#444 has another example of an object that is being made transferable.

@stefhak
Copy link
Contributor

stefhak commented Jan 28, 2016

This PR (and #317 ) needs work. If no one does the work it can't be part of 1.0.

@alvestrand
Copy link
Contributor

Closing while preparing for 1.0. It can be reopened later.

@alvestrand alvestrand closed this Feb 18, 2016
@alvestrand alvestrand removed the LATER label May 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants