Mina2.0框架源码剖析(六).docVIP

上文的内容还有一些没有结尾，这篇补上。在ExpiringMap类中，使用了一个私有内部类ExpiringObject来表示待检查超时的对象，它包括三个域，键，值，上次访问时间，以及用于上次访问时间这个域的读写锁： ????????private?K?key;????????private?V?value;????????private?long?lastAccessTime;????????private?final?ReadWriteLock?lastAccessTimeLock?=?new?ReentrantReadWriteLock(); 而ExpiringMap中包括了下述几个变量: ??private?final?ConcurrentHashMapK,?ExpiringObject?delegate;//超时代理集合，保存待检查对象????private?final?CopyOnWriteArrayListExpirationListenerV?expirationListeners;//超时监听者????private?final?Expirer?expirer;//超时检查线程 现在再来看看IoSession的一个抽象实现类AbstractIoSession。这是它的几个重要的成员变量： ????private?IoSessionAttributeMap?attributes;//会话属性映射图????private?WriteRequestQueue?writeRequestQueue;//写请求队列????private?WriteRequest?currentWriteRequest;//当前写请求 ?????当要结束当前会话时，会发送一个一个写请求CLOSE_REQUEST。而closeFuture这个CloseFuture会在连接关闭时状态被设置为”closed”,它的监听器是SCHEDULED_COUNTER_RESETTER。 close和closeOnFlush都是异步的关闭操作，区别是前者立即关闭连接，而后者是在写请求队列中放入一个CLOSE_REQUEST，并将其即时刷新出去，若要真正等待关闭完成，需要调用方在返回的CloseFuture等待 public?final?CloseFuture?close()?{????????synchronized?(lock)?{????????????if?(isClosing())?{????????????????return?closeFuture;????????????}?else?{????????????????closing?=?true;????????????}????????}????????getFilterChain().fireFilterClose();//fire出关闭事件????????return?closeFuture;????}????public?final?CloseFuture?closeOnFlush()?{????????getWriteRequestQueue().offer(this,?CLOSE_REQUEST);????????getProcessor().flush(this);????????return?closeFuture;????} ?????下面来看看读数据的过程： public?final?CloseFuture?close()?{????????synchronized?(lock)?{?????????????if?(isClosing())?{????????????????return?closeFuture;????????????}?else?{????????????????closing?=?true;????????????}????????}????????getFilterChain().fireFilterClose();//fire出关闭事件????????return?closeFuture;????}????public?final?CloseFuture?closeOnFlush()?{????????getWriteRequestQueue().offer(this,?CLOSE_REQUEST);????????getProcessor().flush(this);????????return?closeFuture;????}????private?QueueReadFuture?getReadyReadFutures()?{//返回可被读数据队列??????