Implementation Differences Between NioClientSocketChannelFactory / OioClientSocketChannelFactory

[Johnny Luong]

I've implemented a more specific test case and it seems to point to a
bug in my code base, so I think all is well.

Johnny Luong wrote:
> Hi,
> 
> I'm experimenting with some a variation of the client socket reconnect
> attempt provided in the examples against Netty 3.2.0.BETA1 and was
> wondering if it is to be expected that the channel should be available
> as part of the channelfuture or not.  In my particular case, the
> endpoint is unavailable and results in a connection refused if an
> attempt is made to connect to it.
> 
> In the NioClientSocketChannelFactory case, the initial connect returns a
> channelfuture containing a channel.  The channel is returned and
> operations like isConnected() perform as expected (either because it
> hasn't completed the connect attempt (returning false) or it did and
> failed (returning false))
> 
> In the OioClientSocketChannelFactory case, the initial connect returns a
> channelfuture and contains no channel.  My initial thought is that it
> should also return a channel but perhaps the operations should block,
> e.g: isConnected()...
> 
> 
> Thanks,
> Johnny

I've implemented a more specific test case and it seems to point to a
bug in my code base, so I think all is well.

Best,
Johnny