WebSocketClientCompressionHandler (Netty API Reference (5.0.0.Alpha4))

java.lang.Object
- io.netty5.handler.codec.http.websocketx.extensions.WebSocketClientExtensionHandler
- - io.netty5.handler.codec.http.websocketx.extensions.compression.WebSocketClientCompressionHandler

All Implemented Interfaces:

ChannelHandler
```
public final class WebSocketClientCompressionHandler
extends WebSocketClientExtensionHandler
```
Extends io.netty5.handler.codec.http.websocketx.extensions.compression.WebSocketClientExtensionHandler to handle the most common WebSocket Compression Extensions. See io.netty5.example.http.websocketx.client.WebSocketClient for usage.

Field Summary

Fields
Modifier and Type Field Description

static WebSocketClientCompressionHandler INSTANCE

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method	Description
`boolean`	`isSharable()`	Returns `true` if this handler is sharable and thus can be added to more than one `ChannelPipeline`.

Methods inherited from class io.netty5.handler.codec.http.websocketx.extensions.WebSocketClientExtensionHandler
channelRead, write

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface io.netty5.channel.ChannelHandler
bind, channelActive, channelExceptionCaught, channelInactive, channelInboundEvent, channelReadComplete, channelRegistered, channelShutdown, channelUnregistered, channelWritabilityChanged, close, connect, deregister, disconnect, flush, handlerAdded, handlerRemoved, pendingOutboundBytes, read, register, sendOutboundEvent, shutdown

- Field Detail
  - INSTANCE
```
public static final WebSocketClientCompressionHandler INSTANCE
```
- Method Detail
  - isSharable
```
public boolean isSharable()
```
    Description copied from interface: ChannelHandler
    
    Returns true if this handler is sharable and thus can be added to more than one ChannelPipeline. By default, this method returns false. If this method returns false, you have to create a new handler instance every time you add it to a pipeline because it has unshared state such as member variables.