public class OioServerSocketChannelFactory extends java.lang.Object implements ServerSocketChannelFactory
ServerSocketChannelFactory
which creates a server-side blocking
I/O based ServerSocketChannel
. It utilizes the good old blocking
I/O API which is known to yield better throughput and latency when there
are relatively small number of connections to serve.
There are two types of threads in a OioServerSocketChannelFactory
;
one is boss thread and the other is worker thread.
Each bound ServerSocketChannel
has its own boss thread.
For example, if you opened two server ports such as 80 and 443, you will
have two boss threads. A boss thread accepts incoming connections until
the port is unbound. Once a connection is accepted successfully, the boss
thread passes the accepted Channel
to one of the worker
threads that the OioServerSocketChannelFactory
manages.
Each connected Channel
has a dedicated worker thread, just like a
traditional blocking I/O thread model.
All threads are acquired from the Executor
s which were specified
when a OioServerSocketChannelFactory
was created. Boss threads are
acquired from the bossExecutor
, and worker threads are acquired from
the workerExecutor
. Therefore, you should make sure the specified
Executor
s are able to lend the sufficient number of threads.
Both boss and worker threads are acquired lazily, and then released when there's nothing left to process. All the related resources are also released when the boss and worker threads are released. Therefore, to shut down a service gracefully, you should do the following:
ChannelGroup.close()
)releaseExternalResources()
.RejectedExecutionException
and the related resources might not be released properly.
A ServerSocketChannel
created by this factory and its child channels
do not support asynchronous operations. Any I/O requests such as
"write"
will be performed in a blocking manner.
构造器和说明 |
---|
OioServerSocketChannelFactory()
Create a new
OioServerSocketChannelFactory with a Executors.newCachedThreadPool()
for the boss and worker executor. |
OioServerSocketChannelFactory(java.util.concurrent.Executor bossExecutor,
java.util.concurrent.Executor workerExecutor)
Creates a new instance.
|
OioServerSocketChannelFactory(java.util.concurrent.Executor bossExecutor,
java.util.concurrent.Executor workerExecutor,
ThreadNameDeterminer determiner)
Creates a new instance.
|
限定符和类型 | 方法和说明 |
---|---|
ServerSocketChannel |
newChannel(ChannelPipeline pipeline)
|
void |
releaseExternalResources()
Releases the external resources that this factory depends on to function.
|
void |
shutdown()
Shudown the ChannelFactory and all the resource it created internal.
|
public OioServerSocketChannelFactory()
OioServerSocketChannelFactory
with a Executors.newCachedThreadPool()
for the boss and worker executor.
See OioServerSocketChannelFactory(Executor, Executor)
public OioServerSocketChannelFactory(java.util.concurrent.Executor bossExecutor, java.util.concurrent.Executor workerExecutor)
bossExecutor
- the Executor
which will execute the boss threadsworkerExecutor
- the Executor
which will execute the I/O worker threadspublic OioServerSocketChannelFactory(java.util.concurrent.Executor bossExecutor, java.util.concurrent.Executor workerExecutor, ThreadNameDeterminer determiner)
bossExecutor
- the Executor
which will execute the boss threadsworkerExecutor
- the Executor
which will execute the I/O worker threadsdeterminer
- the ThreadNameDeterminer
to set the thread names.public ServerSocketChannel newChannel(ChannelPipeline pipeline)
ChannelFactory
newChannel
在接口中 ChannelFactory
newChannel
在接口中 ServerChannelFactory
newChannel
在接口中 ServerSocketChannelFactory
pipeline
- the ChannelPipeline
which is going to be
attached to the new Channel
public void shutdown()
ChannelFactory
shutdown
在接口中 ChannelFactory
public void releaseExternalResources()
ChannelFactory
Executor
s that you specified in the factory
constructor are external resources. You can call this method to release
all external resources conveniently when the resources are not used by
this factory or any other part of your application. An unexpected
behavior will be resulted in if the resources are released when there's
an open channel which is managed by this factory.
This will also call ChannelFactory.shutdown()
before do any actionreleaseExternalResources
在接口中 ChannelFactory
releaseExternalResources
在接口中 ExternalResourceReleasable