The active configuration for this extension.
The <code>Sec-WebSocket-Extensions</code> name for this extension. <p> Also known as the <a href="https://tools.ietf.org/html/rfc6455#section-9.1"><code>extension-token</code> per Section 9.1. Negotiating Extensions</a>.
Used to indicate that the extension makes use of the RSV1 bit of the base websocket framing. <p> This is used to adjust validation during parsing, as well as a checkpoint against 2 or more extensions all simultaneously claiming ownership of RSV1.
Used to indicate that the extension makes use of the RSV2 bit of the base websocket framing. <p> This is used to adjust validation during parsing, as well as a checkpoint against 2 or more extensions all simultaneously claiming ownership of RSV2.
Used to indicate that the extension makes use of the RSV3 bit of the base websocket framing. <p> This is used to adjust validation during parsing, as well as a checkpoint against 2 or more extensions all simultaneously claiming ownership of RSV3.
Set the next {@link IncomingFrames} to call in the chain.
Set the next {@link OutgoingFrames} to call in the chain.
Process the incoming frame. <p> Note: if you need to hang onto any information from the frame, be sure to copy it, as the information contained in the Frame will be released and/or reused by the implementation.
A frame, and optional callback, intended for the network layer. <p> Note: the frame can undergo many transformations in the various layers and extensions present in the implementation. <p> If you are implementing a mutation, you are obliged to handle the incoming WriteCallback appropriately.
Interface for WebSocket Extensions. <p> That {@link Frame}s are passed through the Extension via the {@link IncomingFrames} and {@link OutgoingFrames} interfaces