Hello, As I have understood then we already have similar behavior to what is suggested by Trustin in the situation where the connection fails - a call to ConnectFuture.setException(Throwable). So in that sense this kind of change would be good.
But I have one related problem: the filters which are used by the IoHandler are not used by the ConnectFuture. Do you guys have any suggestions how we could modify the API so that all the executor and logging filters could be called also when using ConnectFuture? This is very much needed when the connection fails - in this case the IoHandler isn't notified at all. May be we should add a method connectFailed() or something similar to the IoHandler? Thanks, Kristjan 2008/1/25, Mark <[EMAIL PROTECTED]>: > > I just ran into this when I was trying to figure out the > DatagramConnectorTest/WinXP bug. I think that if the connection is made > then the signal should be made. So I guess what I am saying is +1. > > > On Jan 24, 2008 4:55 AM, Trustin Lee <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > For now, ConnectFuture is notified right after > > IoHandler.sessionOpened() returns. This sometimes makes people > > confused when sessionOpened() doesn't return immediately. Because the > > connection is already established but ConnectFuture is not being > > notified. > > > > Just calling ConnectFuture.setSession() after sessionCreated() will > > resolve this issue, but will bring another backward-incompatibility > > issue. > > > > What would be the best way to resolve this kind of situation? > > > > Trustin > > -- > > what we call human nature is actually human habit > > -- > > http://gleamynode.net/ > > -- > > PGP Key ID: 0x0255ECA6 > > > > > > -- > -------------------------------- > Talent hits a target no one else can hit; Genius hits a target no one else > can see. >
