public class HttpTransport extends AbstractTcpTransport
| Modifier and Type | Class and Description |
|---|---|
static class |
HttpTransport.Config |
static interface |
HttpTransport.Factory |
static class |
HttpTransport.Handler |
bossExecutor, configuration, connectionCounter, workerExecutorCK_BIND_ADDRESS, CK_PORT, CK_RECV_BUFFER_SIZE, localRegistry, throughputCounter| Constructor and Description |
|---|
HttpTransport(Configuration configuration,
Executor bossPool,
ThroughputCounter throughputCounter,
ConnectionCounter connectionCounter,
LocalMetricRegistry localRegistry) |
| Modifier and Type | Method and Description |
|---|---|
protected LinkedHashMap<String,Callable<? extends org.jboss.netty.channel.ChannelHandler>> |
getBaseChannelHandlers(MessageInput input)
Subclasses can override this to add additional ChannelHandlers to the pipeline to support additional features.
|
protected LinkedHashMap<String,Callable<? extends org.jboss.netty.channel.ChannelHandler>> |
getFinalChannelHandlers(MessageInput input)
Subclasses can override this to modify the
channel handlers at the end of the pipeline. |
getBootstrapgetLocalAddress, getMetricSet, getRecvBufferSize, launch, setMessageAggregator, stoppublic HttpTransport(Configuration configuration, @Named(value="bossPool") Executor bossPool, ThroughputCounter throughputCounter, ConnectionCounter connectionCounter, LocalMetricRegistry localRegistry)
protected LinkedHashMap<String,Callable<? extends org.jboss.netty.channel.ChannelHandler>> getBaseChannelHandlers(MessageInput input)
NettyTransportgetBaseChannelHandlers in class AbstractTcpTransportChannelPipelineFactoryprotected LinkedHashMap<String,Callable<? extends org.jboss.netty.channel.ChannelHandler>> getFinalChannelHandlers(MessageInput input)
NettyTransportchannel handlers at the end of the pipeline.
The default handlers in this group are the aggregation handler (e.g. for chunked GELF via UDP), which can be missing, and the NettyTransport.RawMessageHandler.
Usually this should not be necessary, only modify them if you have a codec that cannot create a RawMessage for
incoming messages at the end of the pipeline.
One valid use case would be to insert debug handlers in the middle of the list, though.getFinalChannelHandlers in class NettyTransportCopyright © 2012-2016 Graylog, Inc.. All Rights Reserved.