[ http://issues.apache.org/jira/browse/DIRMINA-120?page=comments#action_12357550 ]
Trustin Lee commented on DIRMINA-120: ------------------------------------- I thought over your opinion and found the simpler way: http://svn.apache.org/viewcvs/directory/network/trunk/src/java/org/apache/mina/common/IoFuture.java?rev=343990&r1=343989&r2=343990&view=diff If we're going to downcast, why not downcasting IoFuture itself like this? ConnectFuture future = ...; future.setCallback( new Iofuture.Callback() { public void operationComplete( IoFuture future ) { ConnectFuture cf = ( ConnectFuture ) future; try { IoSession session = cf.getSession(); } ... } }); > Callbacks for IoFutures > ----------------------- > > Key: DIRMINA-120 > URL: http://issues.apache.org/jira/browse/DIRMINA-120 > Project: Directory MINA > Type: Improvement > Reporter: Trustin Lee > Assignee: Trustin Lee > Fix For: 0.9 > Attachments: ConnectFuture.java, IoFuture.java > > IoFuture provides only blocking-way ('join' method) for user to find out the > result of an I/O request. It would be great if users can specify a callback: > ConnectFuture future = connector.connect(...); > future.setCallback( new ConnectFuture.Callback() { > public void connectionEstablished( IoSession session ) { > } > public void connectionFailed( Throwable cause ) { > } > } ); > There can be a race condition if the connection process ends before a user > calls setCallback() method, but we can resolve this carefully so users don't > notice any issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
