Lines Matching full:channel
29 // - Another context calls "extension.connect()" to open a channel to the
31 // open a channel to the content scripts for the given tab. The EMS notifies
34 // - Once the channel is established, either side can call postMessage to send
35 // a message to the opposite side of the channel, which may have multiple
39 // channel: connection between two ports
50 // A messaging channel. Note that the opening port can be the same as the
69 // Given an extension's ID, opens a channel between the given renderer "port"
78 // Same as above, but opens a channel to the tab with the given ID. Messages
86 // Given an extension ID, opens a channel between the given
88 // channel will be open to the extension process hosting the
97 // Given an extension ID, opens a channel between the given DevTools
101 // Returns a port ID identifying the DevTools end of the channel, to
108 // Closes the message channel associated with the given port, and notifies
119 // A map of channel ID to its channel object.
124 // Common among Open(Special)Channel* variants.
