org.jactr.tools.async.shadow.handlers
Class LogoutMessageHandler
java.lang.Object
org.jactr.tools.async.shadow.handlers.LogoutMessageHandler
- All Implemented Interfaces:
- org.apache.mina.handler.demux.MessageHandler<LogoutCommand>
public class LogoutMessageHandler
- extends java.lang.Object
- implements org.apache.mina.handler.demux.MessageHandler<LogoutCommand>
logout sequence is really idiotic, the remote interface after all is done
sends the logout command to the shadow controller who just echoes it back.
when the remote interface receives the logout reply it actually disconnects
- Author:
- developer
| Fields inherited from interface org.apache.mina.handler.demux.MessageHandler |
NOOP |
| Methods inherited from class java.lang.Object |
equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
LogoutMessageHandler
public LogoutMessageHandler(BaseIOHandler handler)
handleMessage
public void handleMessage(org.apache.mina.core.session.IoSession session,
LogoutCommand arg1)
throws java.lang.Exception
- Specified by:
handleMessage in interface org.apache.mina.handler.demux.MessageHandler<LogoutCommand>
- Throws:
java.lang.Exception- See Also:
org.apache.mina.handler.demux.MessageHandler#messageReceived(org.apache.mina.common.IoSession,
java.lang.Object)