目前的消息服务的线程模型是在单线程上面实现对socket的读和写,缺点是必须得以轮询的方式去查询是否有可读的数据,虽然轮询间隔时间为400ms,但是仍然占用了一定的系统资源
解决占用系统资源的办法,最直接的是使用两个线程去分别处理socket的读和写,但是这个方式仍然比较原始,需要处理线程间的同步和互斥。
如果采用mina的方式,因为mina是基于事件驱动的,所以比较方便,示例如下:
IoConnector connector = new NioSocketConnector();
connector.setConnectTimeoutMillis(30000);
connector.getFilterChain().addLast(
"codec",
new ProtocolCodecFilter(new TextLineCodecFactory(
Charset.forName("UTF-8"))));
connector.setHandler(new MyIoHandlerAdapter());
ConnectFuture future = connector.connect(new InetSocketAddress(
"192.168.91.109", 4321));
Log.i("Test", "before await");
future.awaitUninterruptibly();
Log.i("Test", "after await");
IoSession session = future.getSession();
session.write("");
session.getCloseFuture().awaitUninterruptibly();
Log.i("Test", "before dispose");
connector.dispose();
Log.i("Test", "after dispose");
public class MyIoHandlerAdapter extends IoHandlerAdapter {
@Override
public void exceptionCaught(IoSession session, Throwable cause)
throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in exceptionCaught");
super.exceptionCaught(session, cause);
}
@Override
public void messageReceived(IoSession session, Object message)
throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in messageReceived");
super.messageReceived(session, message);
}
@Override
public void messageSent(IoSession session, Object message) throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in messageSent");
super.messageSent(session, message);
}
@Override
public void sessionClosed(IoSession session) throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in sessionClosed");
super.sessionClosed(session);
}
@Override
public void sessionCreated(IoSession session) throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in sessionCreated");
super.sessionCreated(session);
}
@Override
public void sessionIdle(IoSession session, IdleStatus status)
throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in sessionIdle");
super.sessionIdle(session, status);
}
@Override
public void sessionOpened(IoSession session) throws Exception {
// TODO Auto-generated method stub
Log.i("Test", "in sessionOpened");
super.sessionOpened(session);
}
}
另外要注意,我之前一直在考虑Java NIO的Selector能不能解决这个问题,其实答案是不能解决,因为Selector面向的需求是有大量的socket需要管理的情况,我们这里是客户端,不存在大量socket的问题。如果有大量的socket链接,那么使用Selector技术就可以实现用两个线程来管理所有的socket的读写,而不必每个socket分配两个线程。