Java NIO Selector
2012-03-07 17:38
405 查看
A
Here is a list of the topics covered in this text:
Why Use a Selector?
Creating a Selector
Registering Channels with a Selector
SelectionKey's
Selecting Channels via a Selector
wakeUp()
close()
Full Example
and each thread takes up some resources (memory) in the operating system too. Therefore, the less threads you use, the better.
Keep in mind though, that modern operating systems and CPU's become better and better at multitasking, so the overheads of multithreading becomes smaller over time. In fact, if a CPU has multiple cores, you might be wasting CPU power by
not multitasking. Anyways, that design discussion belongs in a different text. It suffices to say here, that you can handle multiple channels with a single thread, using a
Here is an illustration of a thread using a
[/code]
[/code]
The
Notice the second parameter of the
Connect
Accept
Read
Write
A channel that "fires an event" is also said to be "ready" for that event. So, a channel that has connected successfully to another server is "connect ready". A server socket channel which accepts an incoming connection is "accept" ready. A channel that
has data ready to be read is "read" ready. A channel that is ready for you to write data to it, is "write" ready.
These four events are represented by the four
SelectionKey.OP_CONNECT
SelectionKey.OP_ACCEPT
SelectionKey.OP_READ
SelectionKey.OP_WRITE
If you are interested in more than one event, OR the constants together, like this:
[/code]
I'll return to the interest set a bit further down in this text.
The interest set
The ready set
The Channel
The Selector
An attached object (optional)
I'll describe these properties below.
[/code]
As you can see, you can AND the interest set with the given
[/code]
You can test in the same way as with the interest set, what events / operations the channel is ready for. But, you can also use these four methods instead, which all reaturn a boolean:
[/code]
[/code]
[/code]
You can also attach an object already while registering the
that are ready for reading from the
Here are the
int select()
int select(long timeout)
int selectNow()
The
When you register a channel with a
You can iterate this selected key set to access the ready channels. Here is how that looks:
[/code]
This loop iterates the keys in the selected key set. For each key it tests the key to determine what the channel referenced by the key is ready for.
Notice the
The channel returned by the
If a different thread calls
[/code]
Selectoris a Java NIO component which can examine one or more NIO Channel's, and determine which channels are ready for e.g. reading or writing. This way a single thread can manage multiple channels, and thus multiple network connections.
Here is a list of the topics covered in this text:
Why Use a Selector?
Creating a Selector
Registering Channels with a Selector
SelectionKey's
Selecting Channels via a Selector
wakeUp()
close()
Full Example
Why Use a Selector?
The advantage of using just a single thread to handle multiple channels is that you need less threads to handle the channels. Actually, you can use just one thread to handle all of your channels. Switching between threads is expensive for an operating system,and each thread takes up some resources (memory) in the operating system too. Therefore, the less threads you use, the better.
Keep in mind though, that modern operating systems and CPU's become better and better at multitasking, so the overheads of multithreading becomes smaller over time. In fact, if a CPU has multiple cores, you might be wasting CPU power by
not multitasking. Anyways, that design discussion belongs in a different text. It suffices to say here, that you can handle multiple channels with a single thread, using a
Selector.
Here is an illustration of a thread using a
Selectorto handle 3
Channel's:
Java NIO: A Thread uses a Selector to handle 3 Channel's |
Creating a Selector
You create aSelectorby calling the
Selector.open()method, like this:
Selector selector = Selector.open();
[/code]
Registering Channels with the Selector
In order to use aChannelwith a
Selectoryou must register the
Channelwith the
Selector. This is done using the
SelectableChannel.register()method, like this:
channel.configureBlocking(false); SelectionKey key = channel.register(selector, SelectionKey.OP_READ);
[/code]
The
Channelmust be in non-blocking mode to be used with a
Selector. This means that you cannot use
FileChannel's with a
Selectorsince
FileChannel's cannot be switched into non-blocking mode. Socket channels will work fine though.
Notice the second parameter of the
register()method. This is an "interest set", meaning what events you are interested in listening for in the
Channel, via the
Selector. There are four different events you can listen for:
Connect
Accept
Read
Write
A channel that "fires an event" is also said to be "ready" for that event. So, a channel that has connected successfully to another server is "connect ready". A server socket channel which accepts an incoming connection is "accept" ready. A channel that
has data ready to be read is "read" ready. A channel that is ready for you to write data to it, is "write" ready.
These four events are represented by the four
SelectionKeyconstants:
SelectionKey.OP_CONNECT
SelectionKey.OP_ACCEPT
SelectionKey.OP_READ
SelectionKey.OP_WRITE
If you are interested in more than one event, OR the constants together, like this:
int interestSet = SelectionKey.OP_READ | SelectionKey.OP_WRITE;
[/code]
I'll return to the interest set a bit further down in this text.
SelectionKey's
As you saw in the previous section, when you register aChannelwith a
Selectorthe
register()method returns a
SelectionKeyobjects. This
SelectionKeyobject contains a few interesting properties:
The interest set
The ready set
The Channel
The Selector
An attached object (optional)
I'll describe these properties below.
Interest Set
The interest set is the set of events you are interested in "selecting", as described in the section "Registering Channels with the Selector". You can read and write that interest set via theSelectionKeylike this:
int interestSet = selectionKey.interestOps(); boolean isInterestedInAccept = interestSet & SelectionKey.OP_ACCEPT; boolean isInterestedInConnect = interestSet & SelectionKey.OP_CONNECT; boolean isInterestedInRead = interestSet & SelectionKey.OP_READ; boolean isInterestedInWrite = interestSet & SelectionKey.OP_WRITE;
[/code]
As you can see, you can AND the interest set with the given
SelectionKeyconstant to find out if a certain event is in the interest set.
Ready Set
The ready set is the set of operations the channel is ready for. You will primarily be accessing the ready set after a selection. Selection is explained in a later section. You access the ready set like this:int readySet = selectionKey.readyOps();
[/code]
You can test in the same way as with the interest set, what events / operations the channel is ready for. But, you can also use these four methods instead, which all reaturn a boolean:
selectionKey.isAcceptable(); selectionKey.isConnectable(); selectionKey.isReadable(); selectionKey.isWritable();
[/code]
Channel + Selector
Accessing the channel + selector from theSelectionKeyis trivial. Here is how it's done:
Channel channel = selectionKey.channel();
Selector selector = selectionKey.selector();
[/code]
Attaching Objects
You can attach an object to aSelectionKeythis is a handy way of recognizing a given channel, or attaching further information to the channel. For instance, you may attach the
Bufferyou are using with the channel, or an object containing more aggregate data. Here is how you attach objects:
selectionKey.attach(theObject); Object attachedObj = selectionKey.attachment();
[/code]
You can also attach an object already while registering the
Channelwith the
Selector, in the
register()method. Here is how that looks:
SelectionKey key = channel.register(selector, SelectionKey.OP_READ, theObject);
Selecting Channels via a Selector
Once you have register one or more channels with aSelectoryou can call one of the
select()methods. These methods return the channels that are "ready" for the events you are interested in (connect, accept, read or write). In other words, if you are interested in channels that are ready for reading, you will receive the channels
that are ready for reading from the
select()methods.
Here are the
select()methods:
int select()
int select(long timeout)
int selectNow()
select()blocks until at least one channel is ready for the events you registered for.
select(long timeout)does the same as
select()except it blocks for a maximum of
timeoutmilliseconds (the parameter).
selectNow()doesn't block at all. It returns immediately with whatever channels are ready.
The
intreturned by the
select()methods tells how many channels are ready. That is, how many channels that became ready since last time you called
select(). If you call
select()and it returns 1 because one channel has become ready, and you call
select()one more time, and one more channel has become ready, it will return 1 again. If you have done nothing with the first channel that was ready, you now have 2 ready channels, but only one channel had become ready between each
select()call.
selectedKeys()
Once you have called one of theselect()methods and its return value has indicated that one or more channels are ready, you can access the ready channels via the "selected key set", by calling the selectors
selectedKeys()method. Here is how that looks:
Set<SelectionKey> selectedKeys = selector.selectedKeys();
When you register a channel with a
Selectorthe
Channel.register()method returns a
SelectionKeyobject. This key represents that channels registration with that selector. It is these keys you can access via the
selectedKeySet()method. From the
SelectionKey.
You can iterate this selected key set to access the ready channels. Here is how that looks:
Set<SelectionKey> selectedKeys = selector.selectedKeys();
Iterator<SelectionKey> keyIterator = selectedKeys.iterator();
while(keyIterator.hasNext()) {
SelectionKey key = keyIterator.next();
if(key.isAcceptable()) {
// a connection was accepted by a ServerSocketChannel.
} else if (key.isConnectable()) {
// a connection was established with a remote server.
} else if (key.isReadable()) {
// a channel is ready for reading
} else if (key.isWritable()) {
// a channel is ready for writing
}
keyIterator.remove();
}
[/code]
This loop iterates the keys in the selected key set. For each key it tests the key to determine what the channel referenced by the key is ready for.
Notice the
keyIterator.remove()call at the end of each iteration. The
Selectordoes not remove the
SelectionKeyinstances from the selected key set itself. You have to do this, when you are done processing the channel. The next time the channel becomes "ready" the
Selectorwill add it to the selected key set again.
The channel returned by the
SelectionKey.channel()method should be cast to the channel you need to work with, e.g a ServerSocketChannel or SocketChannel etc.
wakeUp()
A thread that has called theselect()method which is blocked, can be made to leave the
select()method, even if no channels are yet ready. This is done by having a different thread call the
Selector.wakeup()method on the
Selectorwhich the first thread has called
select()on. The thread waiting inside
select()will then return immediately.
If a different thread calls
wakeup()and no thread is currently blocked inside
select(), the next thread that calls
select()will "wake up" immediately.
close()
When you are finished with theSelectoryou call its
close()method. This closes the
Selectorand invalidates all
SelectionKeyinstances registered with this
Selector. The channels themselves are not closed.
Full Example
Here is a full example which opens aSelector, registers a channel with it (the channel instantiation is left out), and keeps monitoring the
Selectorfor "readiness" of the four events (accept, connect, read, write).
Selector selector = Selector.open();
channel.configureBlocking(false); SelectionKey key = channel.register(selector, SelectionKey.OP_READ);
while(true) {
int readyChannels = selector.select();
if(readyChannels == 0) continue;
Set<SelectionKey> selectedKeys = selector.selectedKeys();
Iterator<SelectionKey> keyIterator = selectedKeys.iterator();
while(keyIterator.hasNext()) {
SelectionKey key = keyIterator.next();
if(key.isAcceptable()) {
// a connection was accepted by a ServerSocketChannel.
} else if (key.isConnectable()) {
// a connection was established with a remote server.
} else if (key.isReadable()) {
// a channel is ready for reading
} else if (key.isWritable()) {
// a channel is ready for writing
}
keyIterator.remove();
}
}
[/code]
相关文章推荐
- Java NIO类库Selector机制解析(上)
- Java NIO:Buffer、Channel 和 Selector
- java NIO selector全面深入理解
- Java NIO 学习(六)--Selector
- Java NIO类库Selector机制解析(下)
- Java NIO 选择器(Selector)的内部实现(poll epoll)(转)
- Java NIO —— Selector(用于SocketChannel)
- java使用selector NIO socket
- Java NIO之Selector
- Java NIO之Selector
- Java NIO类库Selector机制解析(上)
- Java之NIO(二)selector socketChannel
- Java NIO中的Selector和IO复用
- Java基础知识强化之IO流笔记77:NIO之 Selector
- Java NIO 学习笔记 selector 行为机制分析(select操作 cancel操作)
- Java-NIO-Selector
- Java NIO 之 Selector 练习
- Java NIO SocketChannel+Buffer+Selector 详解(含多人聊天室实例)
- Java nio 学习笔记(二) Charset(字符集)与Selector(异步IO)的知识
- Java NIO之SelectorProvider