[erlang-questions] SCTP Accept

[Serge Aleynikov]

SCTP sockets support one-to-one and one-to-many associations. The
one-to-many don't require an accept - the association notifications events
at the server come via the #sctp_assoc_change{} event. From there you could
either route the client-originated messages to association-specific Erlang
pid, or you could peel-off the association into a separate file one-to-one
socket that is more "traditional" for "TCP"-like style of use.

Serge

On Mon, Jan 25, 2016 at 10:47 AM, Tristan Sloughter <t@REDACTED> wrote:

> I'm basically reviving this old thread:
> http://erlang.org/pipermail/erlang-questions/2009-September/046558.html
>
> As far as I can tell an 'acccept' is necessary. It exists at the lower
> level to provide a socket for communicating with the client that made
> the association. Without this you can't spawn a process per client on
> the server side, unless I'm missing something?
>
> Has this simply not mattered because sctp is not supported in most cloud
> networks and such, so it isn't used? Meaning it makes sense for me to
> add an accept interface? Or is it actually not needed somehow and
> associations can be handled in a similar way to what I described without
> a new socket?
>
> --
>   Tristan Sloughter
>   t@REDACTED
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20160125/aea68172/attachment.htm>