[erlang-questions] socket argument for ssl_connection:socket_control

[Danil Zagoskin]

Hi!

It's because a socket in ssl app (TLS, DTLS) is an Erlang process.
Port is used internally only for TCP/UDP transport, and higher-level
operations (handshake, encoding, decoding, etc.) are performed by a
dedicated worker written in Erlang.
A tuple you see is needed to identify that worker. It also contains some
other data, but the main part is the worker pid.

On Sun, Dec 31, 2017 at 4:41 PM, Joe K <goodjoe2049@REDACTED> wrote:

> Why is socket not a port, but a tuple for dtls_connection?
>
> https://github.com/erlang/otp/blob/master/lib/ssl/src/ssl_
> connection.erl#L164
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
>


-- 
Danil Zagoskin | z@REDACTED
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20171231/10850368/attachment.htm>