Request: provide plugin point for custom socket factory in OIO

[chudak]

Just another comment...

In our case we needed to use hostname verification for our SSL connections.
I would have liked to have been able to plug this in somewhere in my handler
chain (e.g. use a callback after the connection was connected) but alas
there is no way to get the underlying socket from any of the netty
interfaces (e.g. channel).

We had to plug this into a custom OioClientSocketPipelineSink, which we had
to build anyways because of the above limitations, since this is where the
actual socket is connected that is created in the OioClientSocketChannel.

I wonder if exposing the ability to bind a callback handler into the socket
config would be helpful. That way it could be registered up the stack and
the callbacks would be handled down in the framework and clients like me
would need to get access to the underlying raw socket.

e.g.

SocketLifecycleCallbackHandler
{
   /*
    * notification of socket lifecycle changes, e.g. SocketState.OPENED,
SocketState.BOUND, SocketState.CONNECTED, etc
    */
   public void stateEntered(SocketState newState, Socket socket);
}

Cheers,

Charles

--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Request-provide-plugin-point-for-custom-socket-factory-in-OIO-tp6521792p6534218.html
Sent from the Netty User Group mailing list archive at Nabble.com.