[erlang-questions] ssl cb_info vs custom socket library

[Magnus Henoch]

Hi all,

I'm trying to use the ssl application together with a custom socket
library, using the cb_info option to pass in the module name.  However,
at some places the ssl application assumes that the socket is a "real"
socket, and calls inet:setopts on it - though
ssl_connection:workaround_transport_delivery_problems specifically
checks for this and avoids inet:setopts if the transport module is not
gen_tcp.

I realise that cb_info is an undocumented option, so I'd appreciate any
opinions before spending more time on this.  Are there any other reasons
why using a different transport callback would not work?  Would a patch
fixing such problems be welcome?

Regards,
Magnus