A io.backchat.hookup.ServerInfo to use as configuration for this server
A by-name param that functions as factory for io.backchat.hookup.HookupServerClient
This is the first place where you can add additional handlers to the pipeline.
This is the first place where you can add additional handlers to the pipeline. The flashpolicy handler and connection tracker have been added at this point. if a message arrives in this handler it's been untouched. This is a great place to register a handler that deals with metrics like bytes read/transferred etc.
The pipeline to configure.
This is the best place to add your application handler.
This is the best place to add your application handler. If you want to use a web framework that uses it's own request abstraction, then this is the place to plug it in.
The pipeline to configure.
If you want to replace the way pings are handled (for example to support sending new lines on a http stream) This is where you can override the handler addition to the pipeline
If you want to replace the way pings are handled (for example to support sending new lines on a http stream) This is where you can override the handler addition to the pipeline
Broadcast a message to all open connections
Broadcast a message to all open connections
the io.backchat.hookup.OutboundMessage to send.
A future with the result of the operation, a io.backchat.hookup.ResultList
The capabilities this server is configured with
The capabilities this server is configured with
a sequence of io.backchat.hookup.ServerCapability objects
A io.backchat.hookup.ServerInfo to use as configuration for this server
Configure the server bootstrap.
Configure the server bootstrap. This is the place to set socket options. By default it sets soLinger to 0, reuseAddress to true and child.tcpNoDelay to true
If you want to replace the way http requests are handled and read this is the place to do it.
If you want to replace the way http requests are handled and read this is the place to do it.
The pipeline to configure
At this point the pipeline has been configured with flashpolicy, ssl, pinging and connection tracking.
At this point the pipeline has been configured with flashpolicy, ssl, pinging and connection tracking. HTTP support has also been added to the pipeline. if websocket related messages arrive in this handler it should send them to upstream. And a http request that is a websocket upgrade request should also be sent upstream.
The pipeline to configure
If you want to override the entire Netty Channel Pipeline that gets created override this method.
If you want to override the entire Netty Channel Pipeline that gets created override this method. But you're basically throwing away all the features of this server.
This is a factory method.
the created org.jboss.netty.channel.ChannelPipeline
The network address/host to listen on.
the org.jboss.netty.logging.InternalLogger to use as logger for this server.
the org.jboss.netty.logging.InternalLogger to use as logger for this server. This logger is shared with the handlers by default so you only ever see a single source of messages The logger has the same name as the server.
The name of this server
Attach blocks of code to be run when the server starts.
Attach blocks of code to be run when the server starts.
the code to execute when the server starts
Attach blocks of code to be run when the server stops
Attach blocks of code to be run when the server stops
the code to execute when the server stops
The port this server listens on.
Start this server
Start this server
Stop this server.
Stop this server.
The version of this server.
The version of this server.
The version number of this server, defaults to the version of the build.
Netty based HookupServer requires netty 3.4.x or later
Usage: