public class OioClientSocketChannelFactory extends Object implements ClientSocketChannelFactory
ClientSocketChannelFactorywhich creates a client-side blocking I/O based
SocketChannel. 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 is only one type of threads in
Channel has a dedicated worker thread, just like a
traditional blocking I/O thread model.
Worker threads are acquired from the
Executor which was specified
OioClientSocketChannelFactory was created (i.e.
Therefore, you should make sure the specified
Executor is able to
lend the sufficient number of threads.
Worker threads are acquired lazily, and then released when there's nothing left to process. All the related resources are also released when the worker threads are released. Therefore, to shut down a service gracefully, you should do the following:
RejectedExecutionExceptionand the related resources might not be released properly.
SocketChannel created by this factory does not support asynchronous
operations. Any I/O requests such as
will be performed in a blocking manner.
|Constructor and Description|
Creates a new instance with a
Creates a new instance.
|Modifier and Type||Method and Description|
Releases the external resources that this factory depends on to function.
public SocketChannel newChannel(ChannelPipeline pipeline)
public void releaseExternalResources()
Executors 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.
Copyright © 2008-2013 The Netty Project. All Rights Reserved.