[erlang-questions] architectural/design overview of Erlang/OTP network stack
Wed Jul 23 22:02:59 CEST 2014
I wonder if someone can point me to any architectural/design
documentation of Erlang's network stack.
I'm interested in seeing how things are coded in Erlang, as opposed to c
implementation (to the extent that Erlang is not making use of underling
operating system network code). I'm assuming that network programming
in Erlang lends itself to a different style than network coding in other
languages (I'm guessing some kinds of packets/transactions are handled
by spawning a process as opposed to creating and linking a buffer.)
Sort of trying to get a feel for how this all works.
It would be cool beyond belief if someone has an overview of "the life
of an http transaction," or some such, that illustrates all the moving
parts, how events and data flow through various modules, and so forth.
Failing that, some pointers into the code.
Thanks very much,
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra
More information about the erlang-questions