Mark an object as not transferable.
object occurs in the transfer list of a
port.postMessage() call, it will be ignored.
In particular, this makes sense for objects that can be cloned, rather than transferred,
and which are used by other objects on the sending side. For example, Node.js marks
ArrayBuffers it uses for its Buffer pool with this.
This operation cannot be undone.
MessagePort to a different
vm Context. The original
object will be rendered unusable, and the returned
MessagePort instance will
take its place.
MessagePort will be an object in the target context, and will
inherit from its global
Object class. Objects passed to the
port.onmessage() listener will also be created in the target context
and inherit from its global
However, the created
MessagePort will no longer inherit from
EventEmitter, and only
port.onmessage() can be used to receive
events using it.
Receive a single message from a given
MessagePort. If no message is available,
undefined is returned, otherwise an object with a single
that contains the message payload, corresponding to the oldest message in the
Generated using TypeDoc