public class OioClientSocketChannelFactory extends Object implements ClientSocketChannelFactory
ClientSocketChannelFactory
which 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 OioClientSocketChannelFactory
;
worker threads.
Each connected 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
when a OioClientSocketChannelFactory
was created (i.e. workerExecutor
.)
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:
ChannelGroup.close()
, andreleaseExternalResources()
.RejectedExecutionException
and the related resources might not be released properly.
A SocketChannel
created by this factory does not support asynchronous
operations. Any I/O requests such as "connect"
and "write"
will be performed in a blocking manner.
Constructor and Description |
---|
OioClientSocketChannelFactory()
Creates a new instance with a
Executors.newCachedThreadPool() as worker executor. |
OioClientSocketChannelFactory(Executor workerExecutor)
Creates a new instance.
|
OioClientSocketChannelFactory(Executor workerExecutor,
ThreadNameDeterminer determiner)
Creates a new instance.
|
Modifier and Type | Method and Description |
---|---|
SocketChannel |
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 OioClientSocketChannelFactory()
Executors.newCachedThreadPool()
as worker executor.
See OioClientSocketChannelFactory(Executor)
public OioClientSocketChannelFactory(Executor workerExecutor)
workerExecutor
- the Executor
which will execute the I/O worker threadspublic OioClientSocketChannelFactory(Executor workerExecutor, ThreadNameDeterminer determiner)
workerExecutor
- the Executor
which will execute the I/O worker threadsdeterminer
- the ThreadNameDeterminer
to set the thread names.public SocketChannel newChannel(ChannelPipeline pipeline)
ChannelFactory
newChannel
in interface ChannelFactory
newChannel
in interface ClientSocketChannelFactory
pipeline
- the ChannelPipeline
which is going to be
attached to the new Channel
public void shutdown()
ChannelFactory
shutdown
in interface 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
in interface ChannelFactory
releaseExternalResources
in interface ExternalResourceReleasable
Copyright © 2008-2014 The Netty Project. All Rights Reserved.