goog.labs.net.webChannel.Channel

Not needed for testchannel.

Allows the handler to override a host prefix provided by the server. Will be called whenever the channel has received such a prefix and is considering its use.

Not needed for testchannel.

Creates a data Uri applying logic for secondary hostprefix, port overrides, and versioning.

Called when creating an XhrIo object. Override in a subclass if you need to customize the behavior, for example to enable the creation of XHR's capable of calling a secondary domain. Will also allow calling a secondary domain if withCredentials (CORS) is enabled.

Not needed for testchannel.

Gets the Uri used for the connection that receives data from the server.

Not needed for testchannel. Gets the result of previous connectivity tests.

Not needed for testchannel.

Gets the Uri used for the connection that sends data to the server.

Gets the http session id.

Gets the parameter name for the http session id.

Gets whether this channel is currently active. This is used to determine the length of time to wait before retrying. This call delegates to the handler.

Returns whether the channel is closed

Callback from ChannelRequest for when the first byte of response body has been received. This is needed for detecting buffering proxies.

Callback from ChannelRequest that indicates a request has completed.

Callback from ChannelRequest for when new data is received

Sets the http session id.

Sets the parameter name for the http session id.

Determines whether to use a secondary domain when the server gives us a host prefix. This allows us to work around browser per-domain connection limits.

If you need to use secondary domains on different browsers and IE10, you have two choices: 1) If you only care about browsers that support CORS (https://developer.mozilla.org/en-US/docs/HTTP_access_control), you can use #setSupportsCrossDomainXhrs and set the appropriate CORS response headers on the server. 2) Or, override this method in a subclass, and make sure that those browsers use some messaging mechanism that works cross-domain (e.g iframes and window.postMessage).

Whether or not this channel uses WHATWG Fetch/streams.